Methods and systems for active shipment management using a container node within a wireless network enabled vehicle

ABSTRACT

Methods and systems are described for active shipment management within a wireless network enabled vehicle that may use an ID node associated with a package, a container node associated with a logistics container, a vehicle node on the vehicle, and a managing node external to the vehicle. In general, the vehicle node broadcasts a management request to the container node related to the package. The container node identifies the ID node associated with the package based upon shipping information included in the management request. The container node verifies the package is on the vehicle via the ID node&#39;s location as determined by the container node. The container node transmits a verification message to the vehicle node to indicate whether the package is verified to be on the vehicle. The vehicle node then transmits a shipment update message to the managing node indicating updated shipping information related to the package.

RELATED APPLICATIONS

The present application claims the benefit of priority to theProvisional Patent Application No. 62/312,155 entitled “Methods,Apparatus, and Systems Using Enhanced Power Profiles, Container Nodes,Multi-Radio Element Nodes, and Node Communication Equipment.”

The present application is also related in subject matter to thefollowing non-provisional patent applications where each also claims thebenefit of priority to the same above-referenced provisional patentapplication: (1) Non-Provisional patent application Ser. No. 15/430,859entitled “Systems, Apparatus, and Methods for Self-Adjusting a BroadcastSetting of a Node in a Wireless Node Network”; (2) Non-Provisionalpatent application Ser. No. 15/433,023 entitled “Methods and Systems forContainer Node-Based Enhanced Management of a Multi-Level Wireless NodeNetwork”; (3) Non-Provisional patent application Ser. No. 15/433,043entitled “Methods and Systems for Motion-Based Management of an EnhancedLogistics Container”; (4) Non-Provisional patent application Ser. No.15/433,074 entitled “Methods and Systems for Motion-Enhanced PackagePlacement Tracking Using a Container Node Associated with a LogisticsContainer”; (5) Non-Provisional patent application Ser. No. 15/433,273entitled “Methods, Apparatus, and Systems for Enhanced Multi-RadioContainer Node Elements Used in a Wireless Node Network”; (6)Non-Provisional patent application Ser. No. 15/434,404 entitled“Methods, Apparatus, and Systems for Improved Node Monitoring in aWireless Node Network”; and (7) Non-Provisional patent application Ser.No. 15/434,425 entitled “Methods, Non-Transitory Computer ReadableMedia, and Systems for Improved Communication Management of a Pluralityof Wireless Nodes in a Wireless Node Network”.

FIELD OF THE DISCLOSURE

The present disclosure generally relates to systems, apparatus andmethods in the field of managed logistics for items (e.g., an object, apackage, a person, a piece of equipment). More particularly, the presentdisclosure relates to various aspects involving systems, apparatus andmethods that leverage an adaptive, context-aware wireless node networkthat may use enhanced power profiles, proactive movement notification,one or dedicated container nodes as node elements in the network,enhanced nodes that deploy multiple radio elements, and/or enhanced nodecommunication management for highly congested operating nodeenvironments.

BACKGROUND

Asset management has always been an important part of commerce, and theability to identify an item and locate its whereabouts may be consideredcore to companies that ship items from one location to another. Forexample, tracking packages is important to organizations of all kinds,whether it be a company keeping track of inventory to be sold in itsstores, or a package delivery provider keeping track of packages beingtransported through its delivery network. To provide quality service, anorganization typically creates and maintains a highly organized networkfor tracking its items—packages, people, objects, etc. Effectivemanagement of such networks allows lower cost, reduced delivery time,and enhanced customer service. And efficient deployment of the networkhelps manage costs.

In addition to tracking packages, parties that ship and receive packagesmay also need information regarding the conditions of the packages, suchas the temperature and humidity of the package. For example, a customerthat has ordered a box of wine may want to monitor the temperature ofthe contents of the box to determine if the temperature and/or humiditygoes above or below a set range. Likewise, the party that ships thepackage may also want to monitor the conditions of the package to ensurethat the content arrives in the proper condition.

Conventionally, this tracking function may be provided by a variety ofknown mechanisms and systems. Machine-readable barcodes are one wayorganizations keep track of items. A retailer, for example, may use barcodes on items in its inventory. For example, items to be sold in aretailer's store may each be labeled with a different machine-readablebar code. In order to keep track of inventory, the retailer typicallyscans or otherwise captures an image of the bar code on each item sothat a back-end part of the retailer's operation can keep track of whatis coming in and leaving their possession from suppliers. In addition,when an item is sold to a consumer, the bar code for that item isscanned or captured to track sales and inventory levels.

Similarly, a package delivery provider may utilize machine-readable barcodes by associating a bar code with packages to be delivered to arecipient. For example, a package may have a bar code corresponding to atracking number for that package. Each time the package goes through atransit checkpoint (e.g., the courier taking initial control of thepackage, the package being temporarily placed in a storage facilitywhile being moved from a pickup point to a delivery location, and thepackage being delivered to the recipient, etc.), the package's bar codemay be scanned. Bar codes, however, have the disadvantage that personnelmust manually scan each bar code on each item in order to effectivelytrack the items.

Radio-frequency identification (RFID) tags are another known mechanismfor tracking items. In contrast to barcodes, RFID tags do not usuallyrequire manual scanning. For example, in a retail context, an RFID tagon an inventory item may be able to communicate with an electronicreader that actively interrogates for a tag and, when it does, itdetects items in a shopping cart and adds the cost of each item to abill for the consumer. The RFID tag usually transfers a coded numberonly when queried or prompted by the reader. RFID tags have also beenused to track items such as livestock, railroad cars, trucks, and evenairline baggage. These tags typically only allow for basic polled oractively interrogated tracking, but do not provide a way to improveasset management using information about the environment in which theitems are tracked.

Sensor-based tracking systems are also known which can provide moreinformation than RFID systems. Shippers, carriers, recipients, and otherparties often wish to know the location, condition, and integrity ofshipments before, during, and after transport to satisfy quality controlgoals, meet regulatory requirements, and optimize business processes.However, such systems are typically expensive given the complexity ofthe sensors, and may provide extraneous and redundant item information.

Systems exist that deploy different types of nodes in a wireless nodenetwork used for logistics related tracking and monitoring operations.Some networks may have a server at a top level, a master node at amiddle level of the network, and a less complex node (generally referredto as an ID node) at a lower level of the network. In someimplementations, it is known to associate and otherwise pair an ID nodewith a shipping item (such as a box, package, product, or otherpackaging for the product being shipped). One problem that may beencountered with such a wireless network of nodes involves thedependence of the ID node on the master node, which can in somesituations create a large overhead burden of communication trafficbetween multiple ID nodes and a master node associated with those IDnodes. Such master node processing burdens may be experienced when thereis an unduly burdensome concentration or density of package ID nodesthat, for example, enter a logistics transport or facility. In such asituation, the master node may face an undesirably dynamic processingload for monitoring and controlling aspects of how the ID nodes need tobe operating.

Further needs exist related to enhanced methods and systems for trackingnodes and their movement while inside containers or vehicles. Stillfurther needs exist in how to better use radio elements of a node whendeployed in such a logistics related wireless node network so to allowfor improved positional awareness when managing items, nodes associatedwith the items, and/or containers for such managed items.

Additionally, the prospect of a dynamic congested operating nodeenvironment may cause communication issues where nodes are not able tocommunicate with other nodes. Thus, there exists a need for improvedways and systems that facilitate an intelligent and adaptive approach tomanaging congested node landscapes so that nodes may still effectivelycommunicate with one another while operating in such a congestedenvironment.

To address these types of requirements and logistics related issues, oneor more systems are needed that may leverage one or more elements of anadaptive, context-aware wireless node network that may use enhancedpower profiles, proactive movement notification, one or dedicatedcontainer nodes as node elements in the network, enhanced nodes thatdeploy multiple radio elements, and/or enhanced node communicationmanagement for highly congested operating node environments

SUMMARY

In the following description, certain aspects and embodiments willbecome evident. It should be understood that the aspects andembodiments, in their broadest sense, could be practiced without havingone or more features of these aspects and embodiments. It should beunderstood that these aspects and embodiments are merely exemplary.

In general, the following disclosure describes a specialized type ofcontainer node is described for use with elements of a hierarchicalwireless node network and deployed to work within a node-enabled vehicleas part of verifying that a package is on the vehicle.

More specifically, one aspect of the disclosure describes a method foractive shipment management within a wireless network enabled vehicleusing an ID node associated with a package being shipped within thevehicle, a container node associated with a logistics container (such asa storage unit) within the wireless network enabled vehicle, a vehiclenode associated with the vehicle, and a managing node external to thevehicle. The method begins with the vehicle node broadcasting amanagement request related to the package being shipped. The containernode receives the broadcasted management request, and then identifiesthe ID node associated with the package based upon shipping informationincluded in the management request. The container node verifies thepackage is on the vehicle based upon a location of the ID node asdetermined by the container node, and then transmits a verificationmessage to the vehicle node. The verification message indicates whetherthe package is verified as being on the wireless network enabledvehicle. In response, the vehicle node then transmits a shipment updatemessage to the managing node. The shipment update message is based uponthe verification message received by the vehicle node and indicatesupdated shipping information related to the package. Such updatedshipping information may be, for example, an unloading instruction forthe package relative to the location of the ID node, an environmentalcondition information related to the package and the location of the IDnode, a package status indicating the package is on the wireless networkenabled vehicle, and/or a package status indicating the package is noton the wireless network enabled vehicle.

This method, in some implementations, may have container node may alsogenerate a control message for the located ID node to adjust anenvironmental control unit associated with the package. The method mayalso, in other implementations, use a weight-related placement scheme.For example, the method may have the container node compare thedetermined location of the ID node to such a weight-related placementscheme stored within the container node; identify an imbalance conditionbased upon shipping information related to the package and the resultingcomparison of the determined location of the ID node and theweight-related placement scheme; and transmit an imbalance warningreflecting the identified imbalance condition to the vehicle node. Themethod may also have the container node generating a location-basedunload instruction related to the package and/or updating alocation-based unload scheme for the vehicle based upon the location ofthe package's ID node.

In another aspect described herein, an active shipment management systemis described as being within a wireless network enabled vehicle and thatinteracts with a managing node external to the vehicle. The system, ingeneral, includes at least an ID node associated with a package beingshipped, a container node, and a vehicle node. The ID node is configuredand operative to broadcast advertising signals when disposed within thevehicle, and the container node operates to receive one or more of thebroadcasted advertising signals from the ID node as part of determininga location of the ID node. The vehicle node is disposed with thevehicle, provides a wireless communication path from within the vehicleto the managing node external to the vehicle, and is configured tobroadcast a management request related to the package being shipped. Inresponse to the broadcasted management request, the container node isfurther operative to receive the broadcasted management request;identify the ID node associated with the package based upon shippinginformation included in the management request; verify the package is onthe vehicle based upon the location of the ID node as determined by thecontainer node; and transmit a verification message to the vehicle nodeindicating whether the package is verified as being on the vehicle. Thevehicle node, in response to the verification message, transmits ashipment update message to the managing node external to the vehicle.The shipment update message is based upon the verification messagereceived by the vehicle node and indicates updated shipping informationrelated to the package.

In still another aspect of the disclosure, another method is describedfor active shipment management within a wireless network enabledvehicle. This method uses an ID node associated with a package beingshipped within the vehicle, a vehicle node disposed within the vehicle,and a managing node external to the vehicle. The method begins with thevehicle node receiving a management request from the managing node overa wireless network connection between the managing node and the vehiclenode. The vehicle node then identifies the ID node associated with thepackage being shipped (e.g., amongst many node-enabled packages withinthe vehicle) based upon shipping information included in the managementrequest. The vehicle node verifies the package is on the wirelessnetwork enabled vehicle based upon a location of the ID node asdetermined by the vehicle node, and then transmits a shipment updatemessage to the managing node. The shipment update message indicateswhether the package is verified as being on the wireless network enabledvehicle and indicates updated shipping information related to thepackage.

Similar to the above method, another aspect of the disclosure includesan active shipment management system within a wireless network enabledvehicle. The system comprises at least an ID node and a vehicle node.The ID node is associated with a package being shipped, and isconfigured to broadcast advertising signals when disposed within thevehicle. The vehicle node is disposed with the vehicle, and includes atleast a first communication interface providing a first wirelesscommunication path from within the vehicle to a managing node externalto the vehicle. The vehicle node further includes a second communicationinterface providing a second wireless communication path to the ID nodewithin the vehicle such that the first wireless communication path isdistinct from the second wireless communication path. The vehicle nodein the system is configured and operative to at least receive amanagement request over the first wireless communication path from themanaging node; receive one or more of the broadcasted advertisingsignals over the second wireless communication path from the ID node aspart of determining a location of the ID node; identify the ID nodeassociated with the package based upon shipping information included inthe management request; verify the package is on the vehicle based uponthe location of the ID node as determined by the vehicle node; andtransmit a shipment update message over the first wireless communicationpath to the managing node, where the shipment update message indicateswhether the package is verified as being on the vehicle and indicatesupdated shipping information related to the package.

Generally stated, each of these aspects respectively effect improvementsto the wireless logistics node technology used to track and monitoritems being shipped. Additional advantages of this and other aspects ofthe disclosed embodiments and examples will be set forth in part in thedescription which follows, and in part will be obvious from thedescription, or may be learned by practice of the invention. It is to beunderstood that both the foregoing general description and the followingdetailed description are exemplary and explanatory only and are notrestrictive of the invention, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate several embodiments according toone or more principles of the invention and together with thedescription, serve to explain one or more principles of the invention.In the drawings,

FIG. 1 is a diagram of an exemplary wireless node network in accordancewith an embodiment of the invention;

FIG. 2 is a more detailed diagram of an exemplary wireless node networkin accordance with an embodiment of the invention;

FIG. 3 is a more detailed diagram of an exemplary ID node device inaccordance with an embodiment of the invention;

FIG. 4 is a more detailed diagram of an exemplary master node device inaccordance with an embodiment of the invention;

FIG. 5 is a more detailed diagram of an exemplary server in accordancewith an embodiment of the invention;

FIG. 6 is a diagram illustrating the structure or format of an exemplaryadvertisement data packet in accordance with an embodiment of theinvention;

FIG. 7 is a diagram illustrating sample content for an exemplaryadvertisement data packet in accordance with an embodiment of theinvention;

FIG. 8 is a state diagram illustrating exemplary states and transitionsbetween the states as part of operations by an exemplary node in awireless node network in accordance with an embodiment of the invention;

FIG. 9 is a diagram illustrating exemplary components of a wireless nodenetwork during an exemplary master-to-ID node association in accordancewith an embodiment of the invention;

FIG. 10 is a diagram illustrating exemplary components of a wirelessnode network during an exemplary ID-to-ID node association in accordancewith an embodiment of the invention;

FIG. 11 is a diagram illustrating exemplary components of a wirelessnode network during an exemplary ID-to-master node query in accordancewith an embodiment of the invention;

FIG. 12 is a diagram illustrating exemplary components of a wirelessnode network during an exemplary alert advertising mode in accordancewith an embodiment of the invention;

FIG. 13 is a diagram illustrating an exemplary location determinationusing master node advertise in accordance with an embodiment of theinvention;

FIG. 14 is a diagram illustrating an exemplary location determinationusing ID node advertise in accordance with an embodiment of theinvention;

FIG. 15 is a diagram illustrating an exemplary location determinationthrough triangulation in accordance with an embodiment of the invention;

FIG. 16 is a diagram illustrating an exemplary location determinationthrough chaining triangulation in accordance with an embodiment of theinvention;

FIG. 17 is a diagram illustrating an example logistics operation usingexemplary components of a wireless node network in accordance with anembodiment of the invention;

FIG. 18 is a flow diagram illustrating an example method for managingshipment of an item using a wireless node network in accordance with anembodiment of the invention;

FIG. 19 is a flow diagram illustrating another example method formanaging shipment of an item using a wireless node network in accordancewith an embodiment of the invention;

FIG. 20 is a diagram illustrating exemplary node packages located in anexemplary vehicle environment in accordance with an embodiment of theinvention;

FIG. 21 is a diagram illustrating exemplary mobile storage units, suchas ULDs, used as containers that help ship node packages in an exemplaryairborne environment in accordance with an embodiment of the invention;

FIGS. 22A-22C are diagrams illustrating exemplary stages of an ID nodemoving through part of an exemplary transit path while associating withdifferent master nodes in accordance with an embodiment of theinvention;

FIG. 23 is a flow diagram illustrating an example method for associationmanagement of a wireless node network in accordance with an embodimentof the invention;

FIG. 24 is a flow diagram illustrating another example method forassociation management of a wireless node network in accordance with anembodiment of the invention;

FIG. 25 is a flow diagram illustrating yet another example method forassociation management of a wireless node network in accordance with anembodiment of the invention;

FIG. 26 is a flow diagram illustrating an exemplary method for contextmanagement of a wireless node network in accordance with an embodimentof the invention;

FIG. 27 is a flow diagram illustrating an exemplary method for locatinga node in a wireless node network based upon observed signal patternsand characteristic indications over a period of time in accordance withan embodiment of the invention;

FIG. 28 is a flow diagram illustrating an exemplary method for locationdetermination by varying a power characteristic of nodes in a wirelessnode network in accordance with an embodiment of the invention;

FIG. 29 is a flow diagram illustrating an exemplary method for locationdetermination using one or more associations of nodes in a wireless nodenetwork in accordance with an embodiment of the invention;

FIG. 30 is a flow diagram illustrating another exemplary method forlocation determination using one or more associations of nodes in awireless node network in accordance with an embodiment of the invention;

FIG. 31 is a flow diagram illustrating yet another exemplary method forlocation determination using one or more associations of nodes in awireless node network in accordance with an embodiment of the invention;

FIG. 32 is a flow diagram illustrating an exemplary method for locationdetermination of a first node in a wireless node network based oncontext data in accordance with an embodiment of the invention;

FIG. 33 is a flow diagram illustrating an exemplary method fordetermining a location using chaining triangulation for one of aplurality of nodes in a wireless node network having a server inaccordance with an embodiment of the invention;

FIG. 34 is a diagram illustrating an exemplary enhanced self-adjustingwireless node system in accordance with an embodiment of the invention;

FIG. 35 is a diagram illustrating further details of an exemplary nodethat uses self-adjusting broadcast code and at least one broadcastprofile as part of the system shown in FIG. 34 in accordance with anembodiment of the invention;

FIG. 36 is a flow diagram illustrating an exemplary method forself-adjusting a broadcast setting of the node in a wireless nodenetwork in accordance with an embodiment of the invention;

FIG. 37 is a diagram illustrating an exemplary enhanced logistics systemfor managing a multi-level wireless node network involving a pluralityof packages in different containers in accordance with an embodiment ofthe invention;

FIG. 38 is a diagram illustrating another exemplary enhanced logisticssystem for managing a multi-level wireless node network with furtherdetails regarding an exemplary container and a related exemplarycontainer node shown with node-enabled packages maintained within thecontainer in accordance with an embodiment of the invention;

FIG. 39 is a diagram illustrating further details of the exemplarycontainer node deployed within a multi-level wireless node network asshown in FIG. 38 where the network operating environment for thecontainer node includes a package ID node associated with a package, afacility master node associated with a facility, and a server inaccordance with an embodiment of the invention;

FIG. 40 is a flow diagram illustrating an exemplary method for managinga multi-level wireless node network having a plurality of package IDnodes at a first level of the network, a container node at a secondlevel of the network, a facility master node at a third level of thenetwork, and a server at fourth level of the network in accordance withan embodiment of the invention;

FIG. 41 is a diagram illustrating an exemplary motion sensing containernode in accordance with an embodiment of the invention;

FIG. 42 is a diagram illustrating an exemplary motion-based managementsystem for a logistics container that uses an exemplary motion sensingcontainer node in accordance with an embodiment of the invention;

FIG. 43 is a flow diagram illustrating an exemplary method formotion-based management of a logistics container in accordance with anembodiment of the invention;

FIG. 44 is a diagram illustrating an exemplary base platform used aspart of an alternative embodiment of a logistics container in accordancewith an embodiment of the invention;

FIG. 45 is a close up diagram illustrating further details of a cornerof the exemplary base platform shown in FIG. 44 in accordance with anembodiment of the invention;

FIG. 46 is a diagram illustrating a cross-sectional view of a firstexemplary type of periphery edge piece from the exemplary base platformshown in FIG. 44 in accordance with an embodiment of the invention;

FIG. 47 is a diagram illustrating a cross-sectional view of a secondexemplary type of periphery edge piece from the exemplary base platformshown in FIG. 44 in accordance with an embodiment of the invention;

FIG. 48 is a diagram illustrating a cross-sectional view of an exemplarybase attachment point used with the first exemplary type of peripheryedge piece from the exemplary base platform shown in FIG. 46 inaccordance with an embodiment of the invention;

FIG. 49 is a diagram illustrating a cross-sectional view of anotherexemplary base attachment point used with the second exemplary type ofperiphery edge piece from the exemplary base platform shown in FIG. 47in accordance with an embodiment of the invention;

FIG. 50 is a diagram illustrating a cross-sectional view of an exemplarycontainer node as attached to the first exemplary type of periphery edgepiece from the exemplary base platform shown in FIG. 46 in accordancewith an embodiment of the invention;

FIG. 51 is a diagram illustrating a cross-sectional view of theexemplary container node as attached to the second exemplary type ofperiphery edge piece from the exemplary base platform shown in FIG. 47in accordance with an embodiment of the invention;

FIG. 52 is a diagram illustrating how a plurality of exemplary packagesmay be disposed relative to the base platform of FIG. 44 when the baseplatform is part of an exemplary motion sensing container in accordancewith an embodiment of the invention;

FIG. 53 is a diagram illustrating an exemplary flexible cover securedover packages and to the base platform of FIG. 44 as part of anexemplary motion sensing container in accordance with an embodiment ofthe invention;

FIG. 54 is a diagram illustrating an embodiment of an exemplary motionsensing container node used for improved tracking of packages placedwithin a logistics container in accordance with an embodiment of theinvention;

FIG. 55 is a diagram illustrating an exemplary motion-based system forimproved tracking of packages placed within one of a group of differentnode-enabled logistics containers in accordance with an embodiment ofthe invention;

FIG. 56 is a flow diagram illustrating an exemplary motion-based methodfor improved tracking of package placement in a logistics containerusing a container node associated with the logistics container inaccordance with an embodiment of the invention;

FIG. 57 is a flow diagram illustrating an exemplary motion-based methodfor improved tracking of package placement relative to a plurality ofcontainer node enabled logistics containers as part of a monitoredloading operation using a wireless node network including at least amanaging node in accordance with an embodiment of the invention;

FIG. 58 is a flow diagram illustrating an exemplary motion-based methodfor improved tracking of package placement in a container node enabledlogistics container in a monitored loading operation involving ID nodeenabled packages and non-node enabled packages in accordance with anembodiment of the invention;

FIG. 59 is a diagram illustrating an exemplary active shipmentmanagement system as deployed within an exemplary wireless networkenabled vehicle in accordance with an embodiment of the invention;

FIG. 60 is a diagram illustrating further details of an exemplary IDnode enabled package maintained within the exemplary wireless networkenabled vehicle as shown in FIG. 59 where the ID node enabled packageincludes an exemplary environmental control unit operative with the IDnode in the package in accordance with an embodiment of the invention;

FIG. 61 is a flow diagram illustrating an exemplary method for activeshipment management within a wireless network enabled vehicle inaccordance with an embodiment of the invention;

FIG. 62 is a flow diagram illustrating additional steps in a furtherembodiment of the exemplary method for active shipment management asshown in FIG. 61 in accordance with an embodiment of the invention;

FIG. 63 is a diagram illustrating an exemplary active shipmentmanagement system as deployed within an exemplary wireless networkenabled vehicle where the vehicle operates as a mobile storage unit forID node enabled packages without using separate containers and containernodes in accordance with an embodiment of the invention;

FIG. 64 is a flow diagram illustrating an exemplary method for activeshipment management within a wireless network enabled vehicle as shownin FIG. 63 in accordance with an embodiment of the invention;

FIG. 65 is a flow diagram illustrating additional steps in a furtherembodiment of the exemplary method for active shipment management asshown in FIG. 64 in accordance with an embodiment of the invention;

FIG. 66 is a diagram illustrating an exemplary enhanced container nodeapparatus disposed as part of a wireless node network capable logisticscontainer and having at least one improved radio transceiver forreception of a node inside of the logistics container as deployed inaccordance with an embodiment of the invention;

FIG. 67 is a diagram of further internal details of an exemplaryenhanced container node having a radio transceiver with dedicated radiounits and corresponding antenna elements in accordance with anembodiment of the invention;

FIG. 68 is a diagram of further internal details of an exemplaryenhanced container node having a radio transceiver with a single radiounit selectively coupled to multiple antenna elements in accordance withan embodiment of the invention;

FIGS. 69A and 69B are, collectively, a flow diagram illustrating anexemplary method implemented by a multi-antenna container node forlocating a package ID node within a storage area of the logisticscontainer in accordance with an embodiment of the invention;

FIG. 70 is a diagram illustrating an exemplary enhanced container nodeapparatus disposed as part of a wireless node network capable logisticscontainer and having at least one improved radio transceiver forreception of a node outside of the logistics container as deployed inaccordance with an embodiment of the invention;

FIG. 71 is a diagram of further internal details of an exemplaryenhanced container node having a radio transceiver with dedicated radiounits and corresponding antenna elements that receive signals fromoutside of a logistics container in accordance with an embodiment of theinvention;

FIG. 72 is a diagram of further internal details of an exemplaryenhanced container node having a radio transceiver with a single radiounit selectively coupled to multiple antenna elements that receivesignals from outside of a logistics container in accordance with anembodiment of the invention;

FIG. 73 is a diagram illustrating a further embodiment of an exemplaryenhanced container node apparatus disposed as part of a wireless nodenetwork capable logistics container and having a first improved radiotransceiver for reception of a node outside of the logistics containerand a second improved radio transceiver for reception of a node insideof the logistics container as deployed in accordance with an embodimentof the invention;

FIG. 74 is a diagram of an exemplary logistics container having antennaelements disposed in an exemplary configuration that is spatiallydisperse along an axis of the logistics container in accordance with anembodiment of the invention;

FIG. 75 is a diagram of an exemplary logistics container having antennaelements disposed in an exemplary configuration spaced at differentcorners of the logistics container in accordance with an embodiment ofthe invention;

FIG. 76 is a diagram illustrating an exemplary embodiment of multiplewireless node network capable logistics containers having axis-locatedantenna elements and positioned within a physical storage that isassociated with a facility master node in accordance with an embodimentof the invention;

FIG. 77 is a diagram illustrating an exemplary embodiment of multiplewireless node network capable logistics containers having corner-locatedantenna elements and positioned within a physical storage that isassociated with a facility master node in accordance with an embodimentof the invention;

FIG. 78 is a flow diagram illustrating an exemplary method of locating amulti-antenna container node enhanced logistics container disposedwithin a physical storage having an associated master node located at afixed position relative to the physical storage, the container node inthe logistics container having at least a container node controller, afirst radio transceiver, and a second radio transceiver in accordancewith an embodiment of the invention;

FIG. 79 is a diagram illustrating an alternative embodiment of alogistics container implemented with an exemplary a logistics storageplatform for securing, storing, and transporting ID node enabledpackages in accordance with an embodiment of the invention;

FIG. 80 is a more detail diagram illustrating an exemplary enhancedcontainer node having multiple antenna elements as deployed as part ofthe exemplary logistics platform shown in FIG. 79 in accordance with anembodiment of the invention;

FIG. 81 is a diagram illustrating another alternative embodiment of alogistics container that uses shelving platforms for securing, storing,and transporting ID node enabled packages in accordance with anembodiment of the invention;

FIG. 82 is a diagram illustrating yet another alternative embodiment ofa logistics container that uses shelving platforms having a baseplatform and side walls in accordance with an embodiment of theinvention;

FIG. 83 is a diagram illustrating an embodiment of an exemplarydedicated multi-radio system and apparatus for logistics node monitoringdisposed in a wireless node network having a plurality of low-level IDnodes and a high-level managing node, wherein each of the low-level IDnodes is associated with one of a plurality of items being shipped inaccordance with an embodiment of the invention;

FIG. 84 is a flow diagram illustrating an exemplary method for logisticsnode monitoring in a wireless node network using a dedicated multi-radiomid-level monitoring node apparatus with a high-level managing node andmultiple low-level ID nodes associated with different items beingshipped in accordance with an embodiment of the invention;

FIG. 85 is a diagram illustrating an alternative embodiment of anexemplary dedicated multi-radio system and apparatus for logistics nodemonitoring disposed in a wireless node network in accordance with anembodiment of the invention;

FIG. 86 is a diagram illustrating another alternative embodiment of anexemplary dedicated multi-radio system and apparatus for logistics nodemonitoring disposed in a wireless node network in accordance with anembodiment of the invention;

FIGS. 87A-87D are related diagrams illustrating an exemplary system oflogistics node elements that include an exemplary server that providesenhanced communication management for a congested node environment inaccordance with an embodiment of the invention;

FIGS. 88A-88B are related diagrams illustrating the exemplary systemshown in FIG. 87A after a time interval has expired and some of thelogistics node elements have moved to where the exemplary serverprovides enhanced communication management for an updated nodeenvironment in accordance with an embodiment of the invention;

FIGS. 89A-89B are related diagrams illustrating the exemplary systemshown in FIG. 87A after a further time interval has expired and some ofthe logistics node elements have moved within a congested nodeenvironment on an exemplary delivery vehicle in accordance with anembodiment of the invention;

FIG. 90 is a diagram illustrating further details of the exemplaryserver used in the system shown in FIGS. 87A-89B to provide enhancedcommunication management for a congested node environment in accordancewith an embodiment of the invention;

FIG. 91 is a flow diagram illustrating an exemplary enhanced method ofcommunication management of a plurality of wireless nodes by a serveroperating in a wireless node network in accordance with an embodiment ofthe invention;

FIGS. 92A-92B are collective a flow diagram illustrating a more detailedexemplary enhanced method of communication management of a plurality ofwireless nodes by a server and a target node's neighboring node(s) asthey interact within a wireless node network in accordance with anembodiment of the invention;

FIG. 93 is a diagram illustrating details of an exemplary modifiedmaster node that uses one or more node management rules to provideenhanced communication management for a congested node environment inaccordance with an embodiment of the invention;

FIG. 94 is a flow diagram illustrating an exemplary enhanced method ofcommunication management of a plurality of wireless nodes by acommunication management master node operating in a wireless nodenetwork in accordance with an embodiment of the invention;

FIGS. 95A-95B are collectively a flow diagram illustrating anotherexemplary enhanced method of communication management of a plurality ofwireless nodes by a communication management master node and a targetnode's neighboring node(s) as they interact within a wireless nodenetwork in accordance with an embodiment of the invention;

FIGS. 96A-96B are collectively a flow diagram illustrating anotherexemplary enhanced method of communication management of a plurality ofwireless nodes by a server and multiple communication management masternodes as they interact within a wireless node network in accordance withan embodiment of the invention;

FIG. 97 is a diagram illustrating details of an exemplary centralizedcommunication management master node (also referred to as a primarymaster node) that controls other master nodes as part of providingenhanced communication management for a congested node environment inaccordance with an embodiment of the invention;

FIGS. 98A-98C are related diagrams illustrating an exemplary system oflogistics node elements that include an exemplary primary master nodethat controls other master nodes as part of providing enhancedcommunication management for a congested node environment in accordancewith an embodiment of the invention; and

FIG. 99 is a flow diagram illustrating an exemplary enhanced method ofcommunication management of a plurality of wireless nodes that leveragesuse of a primary master node that controls other master nodes inaccordance with an embodiment of the invention.

DESCRIPTION OF THE EMBODIMENTS

Reference will now be made in detail to exemplary embodiments. Whereverpossible, the same reference numbers are used in the drawings and thedescription to refer to the same or like parts.

In general, the following describes various embodiments of acontextually aware hierarchical wireless node network that may bemanaged, operated, and applied by principles as set forth herein. Ingeneral, embodiments of the wireless node network may include one ormore lower level devices or nodes (e.g., an ID node) that rely onshorter-range communication with a higher level device or node (e.g., amaster node), which is operative to communicate with a server over adifferent communication path while the lower level node is unable tocommunicate directly with the server. Those skilled in the art willappreciate that such a hierarchy of different functional communicatingnetwork components (generally referred to as network devices) may becharacterized as a network of nodes. Those skilled in the art willappreciate that in some embodiments, the wireless node network mayinclude the server as well as different wireless nodes despite the factthat the server may not be a dedicated wireless component. In otherembodiments, the network may include similar types of wireless nodes ordifferent types of wireless nodes.

Further, those skilled in the art will appreciate that each embodimentdescribed herein effects improvements to particular technologies, suchas active shipment manage of an ID node enabled package using anadaptive, context-aware wireless node network of node elements, such asa container node and vehicle node associated with a wireless networkenabled vehicle (storage unit, delivery van. Each embodiment describes aspecific technological application of one or more nodes that operate insuch a wireless node network where the specific technologicalapplication improves or otherwise enhances such technical fields asexplained and supported by the disclosure that follows.

Those skilled in the art will understand through the following detaileddescription that the nodes may be associated with items (e.g., anobject, a package, a person, a piece of equipment) and may be used toidentify and locate the items while being dynamically programmed duringoperation of the network and while the items move along an anticipatedpath (e.g., a transit path from an origin point to a destination point).The following further describes various embodiments of a wireless nodenetwork, exemplary ways to manage components of a wireless node network,exemplary ways to better determine the location of components of awireless node network, and applications of a wireless node network toenhance logistics operations that rely upon a wireless node network.

Wireless Node Networks

FIG. 1 illustrates a basic diagram of an exemplary wireless node networkin accordance with an embodiment of the invention. The exemplary networkshown in FIG. 1 comprises a server 100 connected to a network 105, whichis also operatively connected to different network components, such as amaster node 110 a and indirectly to an ID node 120 a through master node110 a. Master node 110 a is typically connected to an ID node 120 a viashort-range wireless communications (e.g., Bluetooth® formattedcommunications). Master node 110 a is typically connected to server 100through network 105 via longer-range wireless communication (e.g.,cellular) and/or medium range wireless communication (e.g., wirelesslocal area data networks or Wi-Fi). ID node 120 a is typically a lowcost device that may be easily placed into a package, be integrated aspart of packaging, or otherwise associated with an item to be trackedand located, such as package 130, a person, or object (e.g., vehicle,etc.). Generally, an ID node is capable of communicating directly with amaster node but incapable of communicating directly with the server,while a master node is capable of communicating directly with the serverand separately and directly communicating with other nodes (such as anID node or another master node). The ability to deploy a hierarchy ofnodes within an exemplary wireless node network to distribute tasks andfunctions at the different levels in an efficient and economical mannerhelps to facilitate a wide variety of adaptive locating, tracking,managing, and reporting applications using such a network of nodes asdiscussed in more detail below.

In general, the lower cost, lower complexity ID node 120 a is managed bythe higher complexity master node 110 a and server 100 as part ofkeeping track of the location of ID node 120 a (and the associateditem), thereby providing intelligent, robust, and broad visibility aboutthe location and status of ID node 120 a. In a typical embodiment, IDnode 120 a is first associated with an item (e.g., package 130, aperson, or object). As ID node 120 a moves with the item, the ID node120 a becomes associated with the master node 110 a, and the server 100is updated with such information. Further movement of the ID node 120 aand item may cause the ID node 120 a to disassociate with master node110 a and be handed off to become associated another master node (notshown), after which the server 100 is again updated. As such, the server100 generally operates to coordinate and manage information related tothe ID node 120 a as the item physically moves from one location toanother. Further details of the architecture and functionality of anembodiment of an exemplary ID node and master node as described below inmore detail with respect to FIGS. 3 and 4, while exemplary server 100 isdescribed below in more detail with respect to FIG. 5.

While server 100 is shown connecting through network 105, those skilledin the art will appreciate that server 100 may have a more direct ordedicated connections to other components illustrated in FIG. 1, such asmaster node 110 a, depending upon implementation details and desiredcommunication paths. Furthermore, those skilled in the art willappreciate that an exemplary server may contain a collection ofinformation in a database (not shown in FIG. 1), while multipledatabases maintained on multiple server platforms or network storageservers may be used in other embodiments to maintain such a collectionof information. Furthermore, those skilled in the art will appreciatethat a database may be implemented with cloud technology thatessentially provides networked storage of collections of informationthat may be directly accessible to devices, such as master node 110 a.

Network 105 may be a general data communication network involving avariety of communication networks or paths. Those skilled in the artwill appreciate that such exemplary networks or paths may be implementedwith hard wired structures (e.g., LAN, WAN, telecommunication lines,telecommunication support structures and telecommunication processingequipment, etc.), wireless structures (e.g., antennas, receivers,modems, routers, repeaters, etc.) and/or a combination of both dependingupon the desired implementation of a network that interconnects server100 and other components shown in FIG. 1 in an embodiment of the presentinvention.

Master node 110 a and ID node 120 a are types of nodes. A node isgenerally an apparatus or device used to perform one or more tasks aspart of a network of components. An embodiment of a node may have aunique identifier, such as a Media Access Control (MAC) address or anaddress assigned to a hardware radio like an Internet Protocol 6 (IPv6)identifier. In some embodiments, the node's unique identifier may becorrelated to a shipment identifier (e.g., a shipment tracking number inone example), or may itself be a shipment's tracking reference.

An ID node, such as ID node 120 a, is generally a low cost activewireless device. In one embodiment, an exemplary ID node is atransceiver-based processing or logic unit having a short-range radiowith variable RF characteristics (e.g., programmable RF output powerrange, programmable receiver sensitivity), memory accessible by theprocessing unit, a timer operatively coupled to the processing unit, anda power source (e.g., a battery) that provides power for the circuitryof the ID node. For example, the physical implementation of an exemplaryID node may be small, and, thus, amenable to integration into a package,label, container, or other type of object. In some implementations of anID node, the node is rechargeable while other implementations do notpermit recharging the power source for the ID node. In otherimplementations, the ID node is environmentally self-contained or sealedso as to enable robust and reliable operations in a variety ofenvironmentally harsh conditions.

A master node, such as master node 110 a, generally serves as anintelligent bridge between the ID node 120 a and the server 100.Accordingly, a master node is generally more sophisticated than an IDnode. In one example embodiment, an exemplary master node is a devicehaving a processing or logic unit, a short-range radio (with may havevariable RF characteristics) used for communicating with other nodes (IDnodes and other master nodes), a medium and/or long-range radio forcommunication with the server 100, memory accessible by the processingunit, a timer operatively coupled to the processing unit, and a powersource (e.g., a battery or a wired power supply connection) thatprovides power for the circuitry of the master node. The exemplarymaster node, such as master node 110 a, may be positioned in a knownfixed location or, alternatively, be a mobile unit having dedicatedlocation positioning circuitry (e.g., GPS circuitry) to allow the masternode to determine its location by itself.

While the embodiment illustrated in FIG. 1 shows only a single masternode and a single ID node, those skilled in the art will appreciate thata wireless network consistent with an embodiment of the invention mayinclude a wide array of similar or different master nodes that eachcommunicate with the server 100 and/or other master nodes, and a widevariety of similar or different ID nodes. Thus, the exemplary networkshown in FIG. 1 is a basic embodiment, while the exemplary network shownin FIG. 2 is a more detailed exemplary wireless node network inaccordance with another embodiment of the invention.

Referring now to FIG. 2, another exemplary wireless node network isshown including server 100 and network 105. Here, master nodes 110 a,110 b, 110 c are deployed and connected to network 105 (and by virtue ofthose respective connections, to server 100) as well as to each other.ID nodes 120 a, 120 b, 120 e are shown as connectable or operative tocommunicate via different paths to various master nodes. However, IDnodes 120 c and 120 d are shown in FIG. 2 connected to ID node 120 b butnot to any of the master nodes. This may be the case if, for example, IDnodes 120 b, 120 c, 120 d are associated with different items (e.g.,packages) within a larger container 210 (or grouped together on apallet). In such an example, only ID node 120 b may remain within thewireless communication range of any master node. This may, for example,be because of the positions of the different ID nodes within thecontainer relative to the closest master node, adverse RF shieldingcaused by the container, adverse RF shielding caused by packaging of theitem, or adverse RF shielding caused by other proximate material thatinterferes with radio transmissions (e.g., several packages of metalitems between the ID node and any master node outside the container).Thus, in the illustrated configuration of the exemplary network shown inFIG. 2, ID nodes 120 c and 120 d may be out of range from the masternodes, yet still have an operative communication path to a master nodethrough ID node 120 b.

Indeed, in one example, prior to placement within container 210, ID node120 b may actually be a master node but the changed RF environment whenplacing it in container 210 may interfere with the master node's abilityto locate itself via location signals (e.g., GPS signals) and cause themaster node to temporarily operate as an ID node while still providingcommunications and data sharing with other ID nodes in container 210.

User access devices 200, 205 are also illustrated in FIG. 2 as beingable to connect to network 105, master nodes, and ID nodes. Generally,user access devices 200 and 205 allow a user to interact with one ormore components of the exemplary wireless node network. In variousembodiments, user access devices 200, 205, may be implemented using adesktop computer, a laptop computer, a tablet (such as an Apple iPad®touchscreen tablet), a personal area network device (such as aBluetooth® device), a smartphone (such as an Apple iPhone®), a smartwearable device (such as a Samsung Galaxy Gear™ smartwatch device, or aGoogle Glass™ wearable smart optics) or other such devices capable ofcommunicating over network 105 with server 100, over a wired or wirelesscommunication path to master node and ID nodes. Thus, an exemplary useraccess device may be a mobile type of device intended to be easily moved(such as a tablet or smartphone), and may be a non-mobile type of deviceintended to be operated from a fixed location (such as a desktopcomputer).

As shown in FIG. 2, user access devices 200, 205 are coupled and incommunication with network 105, but each of them may also be incommunication with each other or other network components in a moredirect manner (e.g., via near field communication (NFC), over aBluetooth® wireless connection, over a Wi-Fi network, dedicated wiredconnection, or other communication path).

In one example, a user access device, such as device 200 or 205, mayfacilitate associating an ID node (such as ID node 120 a) with thetracking number of a package at the start of a shipment process,coordinating with the server 100 to check on the status and/or locationof the package and associated ID node during transit, and possiblyretrieving data from a master node or ID node related to the shippedpackage. Thus, those skilled in the art will appreciate that a useraccess device, such as devices 200, 205, are essentially interactivecommunication platforms by which a user may initiate shipment of anitem, track an item, determine the status and location of an item, andretrieve information about an item.

An exemplary user access device, such as device 200 or 205, may includesufficient hardware and code (e.g., an app or other program code sectionor sections) to operate as a master node or an ID node in variousembodiments as discussed in more detail below. For example, device 200may be implemented as a mobile smartphone and functionally may operateas an exemplary ID node that broadcasts advertising packet messages toother ID nodes or master nodes for association and sharing data withsuch nodes. In another example, device 200 is implemented as a mobilesmartphone and may operate as an exemplary master node that communicatesand associates with ID nodes and other master nodes, as describedherein, and communicates with the server 100. Thus, those skilled in theart will appreciate an exemplary ID node in FIG. 3 and an exemplarymaster node in FIG. 4, and their respective parts, code and programmodules, may be implemented with an appropriately programmed user accessdevice, such as device 200 or 205. Thus, the following description of anexemplary ID node in FIG. 3 and an exemplary master node in FIG. 4 willbe applicable to a user access device operating as an ID node or amaster node, respectively.

ID Node

FIG. 3 is a more detailed diagram of an exemplary ID node device inaccordance with an embodiment of the invention. As previously described,one embodiment of an ID node includes a transceiver-based processing orlogic unit having a short-range radio with variable RF characteristics(e.g., programmable RF output power range, programmable receiversensitivity), memory accessible by the processing unit, a timeroperatively coupled to the processing unit, and a power source (e.g., abattery) that provides power for the circuitry of the ID node. Referringnow to the more detailed embodiment of FIG. 3, exemplary ID node 120 ais shown to comprise a processing or logic unit 300 coupled to avariable power short-range communication interface 375, memory storage315, volatile memory 320, timer 370, and battery 355. Those skilled inthe art will appreciate that processing unit 300 is logic, such as a lowpower consumption microcontroller, that generally performs computationson data and executes operational and application program code and otherprogram modules or sections thereof within the ID node 120 a. As such,exemplary processing unit 300 operates as a transceiver-based processingcore of ID node 120 a.

Those skilled in the art will also appreciate that exemplary ID node 120a is a hardware-based component that may be implemented with a singleprocessor or logic unit, such as unit 300. In one embodiment, processingunit 300 may be implemented with an Intel® 8051 CPU Core and associatedperipheral circuitry as dictated by the needs of the particularapplication. Less complex microcontrollers or discrete circuitry may beused to implement processing unit 300 as well as more complex andsophisticated microprocessors. Additionally, exemplary processing unit300 may be integrated into a single chip transceiver used as a core ofID node 120 a.

The variable power short-range communication interface 375 of ID node120 a is generally a programmable radio and an omni-directional antennacoupled to the processing unit 300. In other embodiments, interface 375may use an antenna with a different antenna profile when directionalitymay be desired. Examples of variable power short-range communicationinterface 375 may include other interfacing hardware (not shown) foroperatively coupling the device to a specific short-range communicationpath (e.g., a Bluetooth® Low Energy (BLE) connection path communicatingat 2.4 GHz).

In one embodiment, various RF characteristics of the radio'stransceiver, such as the RF output power and/or the RF receiversensitivity may be dynamically and programmatically varied under controlof processing unit 300. In other embodiments, further RF characteristicsof the radio's transceiver may be programmatically varied, such asfrequency, duty cycle, timing, modulation schemes, spread spectrumfrequency hopping aspects, etc., as needed to flexibly adjust the RFoutput signal depending upon a desired implementation and anticipateduse of ID node 120 a. As will be explained in more detail below, someembodiments may use Broadcast Profile having parameters that may beprogrammatically altered or adjusted. In other words, embodiments of IDnode 120 a (or any other ID node) may have programmatically adjustableRF characteristics (such as an adjustable RF output signal power, anadjustable RF receiver sensitivity, the ability to switch to a differentfrequency or frequency band, etc.).

The battery 355 for ID node 120 a is a type of power source thatgenerally powers the circuitry implementing ID node 120 a. In oneembodiment, battery 355 may be a rechargeable power source. In otherembodiments, battery 355 may be a non-rechargeable power source intendedto be disposed of after use. In some embodiments of an ID node, thepower source may involve alternative energy generation, such as a solarcell.

The timer 370 for ID node 120 a generally provides one or more timingcircuits used in, for example, time delay, pulse generation, andoscillator applications. In an embodiment where ID node 120 a conservespower by entering a sleep or dormant state for a predetermined timeperiod as part of overall power conservation techniques, timer 370assists processing unit 300 in managing timing operations. Additionally,an embodiment may allow an ID node to share data to synchronizedifferent nodes with respect to timer 370 and a common timing referencebetween nodes and the server.

An embodiment may implement ID node 120 a to optionally include a basicuser interface (UI) 305 indicating status and allowing basic interactionlike start/stop. In one embodiment, the UI 305 may be implemented withstatus lights, such as multi-mode LEDs. Different colors of the lightsmay indicate a different status or mode for the ID node 120 a (e.g., anadvertising mode (broadcasting), a scanning mode (listening), a currentpower status, a battery level status, an association status, an error,as sensed condition (e.g., exceeding a temperature threshold, exceedinga moisture threshold, and the like)). Other embodiments of an ID nodemay implement U! 305 in a more sophisticated manner with a graphicsdisplay or the like where such status or mode information may bedisplayed as well as one or more prompts.

In a further embodiment, an exemplary status light used as part of theUI 305 of an ID node may also indicate a shipment state. In more detail,an exemplary shipment state may include a status of the shipped item ora status of the item's current shipment journey from an origin to adestination.

An embodiment may also implement ID node 120 a to optionally include oneor more sensors 360. In some embodiments, an ID node implemented withone or more sensors 360 may be referred to as a Sensor node. Examples ofsensor 360 may include one or more environmental sensors (e.g.,pressure, movement, light, temperature, humidity, magnetic field,altitude, attitude, orientation, acceleration, etc.) and dedicatedlocation sensors (e.g., GPS sensor, IR sensor, proximity sensor, etc.).Those skilled in the art will understand that additional types ofsensors that measure other characteristics are contemplated for use assensor 360. Additionally, those skilled in the art will understand thata Sensor node may include additional program features to manage thecollection, storage, sharing, and publication of the captured sensordata.

An embodiment may further implement ID node 120 a to optionally includeone or more magnetic switches 365. A magnetic switch 365, such as a reedswitch, generally operates to close or open an electrical path orconnection in response to an applied magnetic field. In other words,magnetic switch 365 is actuated by the presence of a magnetic field orthe removal of a magnetic field. Various applications, as discussed inembodiments described in more detail below, may involve the operation ofID node 120 a having magnetic switch 365.

Consistent with the embodiment shown in FIG. 3, exemplary ID node 120 amay be implemented based upon a Texas Instruments CC2540 Bluetooth® LowEnergy (BLE) System-on-Chip, which includes various peripherals (e.g.,timer circuitry, USB, USART, general-purpose I/O pins, IR interfacecircuitry, DMA circuitry) to operate as an ID node and, if necessary, tointerface with different possible sensors and other circuitry (e.g.,additional logic chips, relays, magnetic switches) that make up the IDnode.

In additional embodiments, one skilled in the art will appreciate thatsimilar functionality in an ID node may be implemented in other types ofhardware. For example, ID node 110 a may be implemented with speciallyoptimized hardware (e.g., a particular application specific integratedcircuit (ASIC) having the same operational control and functionality asnode control and management code, as described below, discrete logic, ora combination of hardware and firmware depending upon requirements ofthe ID node, such as power, processing speed, level of adjustability forthe RF characteristics, number of memory storage units coupled to theprocessor(s), cost, space, etc.

As noted above, ID node 120 a includes memory accessible by theprocessing unit 300. Memory storage 315 and volatile memory 320 are eachoperatively coupled to processing unit 300. Both memory componentsprovide programming and data elements used by processing unit 300. Inthe embodiment shown in FIG. 3, memory storage 315 maintains a varietyof program code (e.g., node control and management code 325) and otherdata elements (e.g., profile data 330, security data 335, associationdata 340, shared data 345, sensor data 350, and the like). Memorystorage 315 is a tangible, non-transient computer readable medium onwhich information (e.g., executable code/modules, node data, sensormeasurements, etc.) may be kept in a non-volatile and non-transitorymanner. Examples of such memory storage 315 may include a hard diskdrive, ROM, flash memory, or other media structure that allows longterm, non-volatile storage of information. In contrast, volatile memory320 is typically a random access memory (RAM) structure used byprocessing unit 300 during operation of the ID node 120 a. Upon power upof ID node 120 a, volatile memory 320 may be populated with anoperational program (such as node control and management code 325) orspecific program modules that help facilitate particular operations ofID node 120 a. And during operation of ID node 120 a, volatile memory320 may also include certain data (e.g., profile data 330, security data335, association data 340, shared data 345, sensor data 350, and thelike) generated as the ID node 120 a executes instructions as programmedor loaded from memory storage 315. However, those skilled in the artwill appreciate that not all data elements illustrated in FIG. 3 mustappear in memory storage 315 and volatile memory 320 at the same time.

Node Control & Management Code

Generally, an embodiment of node control and management code 325 is acollection of software features implemented as programmatic functions orprogram modules that generally control the behavior of a node, such asID node 120 a. In an embodiment, the functionality of code 325 may begenerally similar as implemented in different types of nodes, such as amaster node, an ID node, and a sensor node. However, those skilled inthe art will appreciate that while some principles of operation aresimilar between such nodes, other embodiments may implement thefunctionality with some degree of specialization or in a differentmanner depending on the desired application and use of the node.

In a general embodiment, exemplary node control and management code 325may generally comprise several programmatic functions or program modulesincluding (1) a node advertise and query (scan) logic manager (alsoreferred to herein as a node communications manager), which manages howand when a node communicates; (2) an information control and exchangemanager, which manages whether and how information may be exchangedbetween nodes; (3) a node power manager, which manages power consumptionand aspects of RF output signal power and/or receiver sensitivity forvariable short-range communications; and (4) an association managerfocusing on how the node associates with other nodes. What follows isdescription of various embodiments of these basic program modules usedby nodes.

Node Communications Manager—Advertising & Scanning

In an exemplary embodiment, the node advertise and query (scan) logicmanager governs how and when a node should advertise (transmit) itsaddress or query (scan) for the address of neighboring nodes.Advertising is generally done with a message, which may have differentinformation in various parts (e.g., headers, fields, flags, etc.). Themessage may be a single or multiple packets.

In the exemplary embodiment, the “advertise” mode (as opposed to “query”or “scan” mode) is a default mode for an ID Node and has the nodebroadcasting or transmitting a message with its address and relatedmetadata regarding the node. For example, in one embodiment, exemplarymetadata may include information such as the RF output power level, areference number, a status flag, a battery level, and a manufacturername for the node.

FIG. 6 is a diagram illustrating the structure or format of an exemplaryadvertisement data packet in accordance with a general embodiment of theinvention. Referring now to FIG. 6, the structure of an exemplaryadvertisement data packet 600 broadcast as a signal or message from anID node, such as ID node 120 a, is shown. Packet 600 appears with anincreasing level of detail showing exemplary metadata and a format thatseparately maintains distinct types of metadata in different parts ofthe packet. Different embodiments may include different types ofmetadata depending on the deployed application of the ID node.

FIG. 7 is a diagram illustrating sample content for an exemplaryadvertisement data packet in accordance with an embodiment of theinvention. Referring now to FIG. 7, an exemplary advertisement datapacket 700 is illustrated with exemplary metadata including showingsample information such as the RF Output Power level (e.g., “TX PowerLevel”), a reference number (e.g., “‘FDX ID’ (ASCII Short Name)”, astatus flag (e.g., “Status Flag Value (indicates ‘Ack Requested’)”), abattery level (e.g., “Battery Level Value (Indicates 73% charge)”, and amanufacturer name for the node (e.g., “Company Identifier (currentlyundefined for FedEx)”). In one embodiment, those skilled in the art willappreciate that the reference number may be omitted or obfuscated forsecurity purposes.

In one embodiment, an exemplary advertising data packet may include theRF Output power level, as noted above in FIG. 7, to enable one way tohelp identify the type of node doing the broadcasting and the locationof the broadcasting node. However, if the broadcast RF output powerlevel is fixed and known by the node type, only the node type need beidentifiable from an exemplary advertising data packet, such as packet700.

Regarding how a node communicates, an exemplary node may be in one ofseveral different communication modes. A node in an advertising (ortransmit or broadcast) mode is visible to any other node set in a query(or scan or listen) mode. In an embodiment, the frequency and length ofadvertising may be application and power dependent. For example, innormal operations, an exemplary node will generally advertise in aperiodic manner and expect to make an active connection to another nodeat certain intervals, which may be dictated by conditions set by server100. In an embodiment, such conditions may be set individually for anode by the server or a higher level node in the network.

If an exemplary node has not received acknowledgement for an advertisingpacket within a particular period, it may enter one or more alertstages. For example, if an exemplary node has not receivedacknowledgement from another node for an advertising packet broadcast bythe exemplary node within a particular time period (also generallyreferred to as an Alert Interval), the exemplary node will enter anAlert Stage 1 status. This prompts the exemplary node to issue afollow-up advertising packet having one or more parts of it altered toindicate the Alert Stage 1 status. In more detail, this exemplaryfollow-up advertising packet may have a different advertising alertheader instructing nearby nodes to send a SCAN_REQ message uponreceiving an advertisement packet.

If an exemplary node has not received acknowledgement from a master nodefor an advertising packet broadcast by the exemplary node within anothertime period (e.g., a request from the master node to actively connectand a success connection made), it will enter another alert stage, suchas an Alert Stage 2 status. This prompts the exemplary node to issue afollow-up advertising packet having one or more parts of it altered toindicate the Alert Stage 2 status. In more detail, this exemplaryfollow-up advertising packet may have a different advertising alertheader instructing nearby master nodes to send a SCAN_REQ message uponreceiving an advertisement packet.

If an exemplary node has data to upload to the backend, it may alsoenter another type of alert stage. In one embodiment, for example, if anexemplary node has sensor data collected by the exemplary node (orreceived from one or more other nodes that have communicated with theexemplary node), and the data needs to be uploaded to server 100, theexemplary node may enter an update alert stage, such as an Alert Stage3. This prompts the exemplary node to issue a follow-up advertisingpacket having one or more parts of it altered to indicate the AlertStage 3 status. In more detail, this exemplary follow-up advertisingpacket may have a different advertising alert header instructing nearbymaster nodes to make a connection with the exemplary node so that thedata (e.g., sensor data 350) may be transmitted from the exemplary node(e.g., ID node 120 a) to a nearby master node (e.g., master node 110 a).The transmitted data may then be stored by the nearby master node assensor data 450 in either or both of the master node's volatile memory420 and memory storage 415. Subsequent to that storage operation, thenearby master node will transfer the data (e.g., sensor data 450) toserver 100.

As illustrated in FIG. 7 and explained in the above description of alertlevel stages, a status flag in a header of an exemplary advertising datapacket is a field used in the association logic in one or moreembodiments. For example, in one embodiment, the existence of a statusflag in the advertising data packet allows a first node to communicateits status to a second node, and for the second node to report thatstatus to the backend server, such as server 100, without an activedirect connection from the first node to the server. In other words, thestatus flag helps facilitate passive interactions between nodes (such aspassive associations).

In a more detailed embodiment, several exemplary status types areestablished with respect to communications with other nodes. Forexample, the exemplary status types may comprise the following:

-   -   Alert Level 0—no issue, operating normal;    -   Alert Level 1—The advertising node is requesting that any        available node acknowledge the receipt of its advertisement        packet;    -   Alert Level 2—The advertising node is requesting that any        available master node acknowledge the receipt of its        advertisement packet;    -   Alert Level 3—Data for Upload—node has captured data available        for upload through a master node; and    -   Synchronize—The advertising node requests to connect with a        device or sensor that can synchronize data (such as timer or        location information).

By broadcasting the status via, for example, a portion of a header in anadvertising data packet, one or more nodes within range of thebroadcasting node can determine the node's status and initiate activeconnections if requested in the status message.

A request for more information from the advertising node may, in someembodiments, come in the form of a SCAN_REQ message. In general, anexemplary SCAN_REQ is a message sent from a scanning (listening) masternode to an advertising node requesting additional information from theadvertising node. In this example, the alert status bit may indicate tothe scanning master node, for example, at an application layer, whetherthe advertising node is in a mode that will or will not accept aSCAN_REQ. In one embodiment, the non-connectable and discoverable modesof node advertising are in compliance with Bluetooth® Low Energy (BLE)standards.

In another embodiment, a node may have further different modes ofoperation while scanning or listening for other nodes. For example, anode's query or scanning mode may be active or passive. When a node isscanning while passive, the node will receive advertising data packets,but will not acknowledge and send SCAN_REQ. However, when a node isscanning while active, the node will receive advertising data packets,and will acknowledge receipt by sending a SCAN_REQ. A more detailedembodiment may provide the passive and active modes of scanning orinquiry in compliance with Bluetooth® Low Energy (BLE) standards.

In an embodiment, an exemplary node is scanning as it listens for otherwireless nodes broadcasting on the short-range radio. An exemplaryscanning node may capture, for example, a MAC address of the advertisingnode, a signal strength of the RF output signal transmitted from theadvertising node, and any other metadata published by the advertisingnode (e.g., other information in the advertising data packet). Thoseskilled in the art will appreciate that the scope of “listening” when anode is scanning may vary. For example, the query may be limited. Inother words, the scope of what a node is particularly interested in andfor which it is listening may be focused or otherwise limited. In such acase, for example, the information collected may be limited toparticular information from a targeted population of short-rangewireless nodes advertising; but the information collection may beconsidered “open” where information from any advertising device iscollected.

When nodes are advertising or scanning, an embodiment may make furtheruse of status flags and additional modes when advertising or scanning aspart of how nodes communicate and may be managed. In one example, when ascanning (listening) node receives an advertising data packet with thestatus flag indicating an Alert Level 1 or 2 status, and the scanningnode is in “Passive” scanning mode, the node will switch to “Active”scanning mode for some interval. However, when the scanning node in thissituation is already in an “Active” scanning mode, the node will sendthe SCAN_REQ message and receive a SCAN_RSP from the advertising node(e.g., a message providing the additional information requested from theadvertising node). The scanning node will then switch back to a“Passive” scanning mode.

In another example, when an advertising (broadcasting) node receives aSCAN_REQ from a scanning node, the advertising node will consider thatits advertising data packet has been acknowledged. Further, theadvertising node will reset its “Alert” status flag back to an AlertLevel 0 status. This allows the advertising node to effectively receivean acknowledgement to its advertisement without ever making a connectionto the scanning node, which advantageously and significantly saves onpower consumption.

In yet another example, when a scanning node receives an advertisingdata packet with an Alert Level 3 status flag set, the scanning nodewill attempt to make a connection with the advertising device. Once theconnection is made, the advertising device will attempt to upload itsdata to the connected device

Thus, an embodiment of the node advertise and query (scan) logic managerof code 325 may rely upon one or more status flags, advertising modes,scanning modes, as nodes communicate with each other in variousadvantageous manners.

Node Information Control & Exchange Manager

In an exemplary embodiment, the information control and exchange managerpart of node control and management code 325 determines whether and howinformation may be exchanged between nodes. In the exemplary embodiment,the information control and exchange manager establishes different nodeoperational states where information may be changed according to adesired paradigm for the state. In more detail, an embodiment ofinformation control and exchange manager may establish different levelsof information exchange between nodes with a “non-connectableadvertising” state or mode of operation, a “discoverable advertising”state or mode, and a “general advertising” state or mode operation. Whena node is in the “non-connectable advertising” mode, the nodeinformation exchange is limited. For example, the advertising node maybroadcast information that is captured by one or more querying(scanning) nodes, but no two-way exchange of information happens.

When a node is in the “discoverable advertising” mode and a scanningnode is in “Active” mode, the node information exchange in enabled bothways. For example, the advertising node sends the advertising packet,and in response the scanning node sends the SCAN_REQ packet. After theadvertising node receives the SCAN_REQ requesting additionalinformation, the advertising node sends the SCAN_RSP with the requestedinformation. Thus, in the “discoverable advertising” mode there is atwo-way exchange of information, but no active connection is madebetween the two nodes exchanging information.

Finally, for advanced two-way information exchange, an active connectionmay be used between nodes and information may be exchanged both ways toand from different nodes. In a more detailed embodiment, at this levelof two-way information exchange, nodes are first identified and thenauthenticated as part of establishing the active connection. Onceauthenticated and thereafter actively connected to each other, the nodesmay securely share information back and forth. In one example, a sensornode uploading previously captured environmental information to a masternode may be in this mode or state. In another example, an ID nodeuploading the stored results of a node scanning operation to a masternode may be in this mode or state. In yet another example, a master nodesharing a timer and/or location information with corresponding nodes maybe in this mode or state.

Node Power Manager

In an exemplary embodiment, the node power manager part of node controland management code 325 focuses on managing power consumption and theadvantageous use of power (e.g., an adjustable level of RF output signalpower) in a node. In general, nodes are either powered by a battery(such as battery 355 in an ID node), or by an interface (such asbattery/power interface 470 in a master node) to an external powersource. Examples of an external power source may include, in someembodiments, power supplied from an outlet or power connection within afacility, or power generated onboard a conveyance (e.g., automobile,truck, train, aircraft, ship, etc.). Those skilled in the art willappreciate that an interface to an external power source will begenerally referred to as a “wired” power connection, and that node powermanager may be informed whether a node is wired or powered off abattery, such as battery 355. Further embodiments may implement aninterface to an external power source with wireless power transmission,such as via inductive coils.

In one embodiment, a node may manage power used when performing tasks.For example, a node may manage power when determining which node shouldperform a particular task. In more detail, the collective powerconsumption of a group of devices may be managed by electing to employwired nodes, when feasible or desired, to accomplish a particular task,and saving the battery-powered nodes for other less energy burdensome ortaxing tasks. In another embodiment, historic data may inform the systemof the power needed to accomplish a particular task, and the system maymake a determination of which node should accomplish the particular taskbased upon such historic data. In other embodiments, profile data mayalso be used to inform the system of the power needed to accomplish aparticular task (e.g., a sensor profile that describes powerrequirements for operation of a sensor node that gathers sensor dataover a certain period of time and under certain conditions). The systemmay also make a determination of which node should accomplish theparticular task based upon such profile data.

In another example, the exemplary node power manager may manage powerwhen determining how to best to use and adjust power to more accuratelyaccomplish a particular task. In one embodiment, an RF signal outputfrom a node (such as a short-range RF output signal from an ID node) mayperiodically move through a range of output power or simply switchbetween two or more settings that differ in a detectable manner. Asdisclosed in more detail below, the variability and dynamic adjustmentof RF output signal power may allow other nodes (such as one or moremaster nodes) to see each node at the upper range of the RF outputsignal power, and only see nodes physically close to the advertisingnode at the lower range of signal power.

In another example, the exemplary node power manager may cause a changeto a characteristic of its RF output signal power when the node has beenassociated to a physical place or another node by virtue of context data(such as context data 560 and association logic that utilizes that typeof information). In one embodiment, the node may be instructed to changehow often the node communicates and/or a characteristic of its RF outputpower to preserve power.

In yet another example, all advertising nodes may have their respectivenode power managers periodically cause each respective node to broadcastat a maximum RF output signal power level to ensure they still arewithin range of a scanning ID Node or Master Node. Doing so may increasethe chance of being in communication range and allows the individualnodes to be properly located and managed within the network. Thebroadcast duration may be set or dynamically changed to allow pairing tooccur if needed.

Rather than adjust the RF output signal power level, the exemplary nodepower manager may, in some embodiments, adjust the RF receiversensitivity of a node. This allows for an adjustable range of reception(as opposed to merely an adjustable range of broadcast), which maysimilarly be used to manage power and enhance location determinations asdiscussed herein.

In yet another embodiment, a combination approach may be used in whichthe node power manager may concurrently and independently adjust morethan one RF characteristic of a node. For example, an exemplary nodepower manager may adjust an RF output signal power level and also adjustthe RF receiver sensitivity of a node as the node is located andassociated with other nodes. Those skilled in the art will realize thatthis may be especially useful in an area with an unusually denseconcentration of nodes, and a combination of changing RF output signalpower levels

An embodiment of the exemplary node manager may refer to a power profile(e.g., an exemplary type of profile data 330, 430) when adjusting anode's power characteristics (e.g., consumption of power, use of power,output signal frequency, duty cycle of the output put signal, timing,power levels, etc.).

Node Association Manager

In an exemplary embodiment, the node association manager part of nodecontrol and management code 325 focuses on how the nodes associate withother nodes in conjunction and consistent with the server-sideassociation manager in code 525, as discussed in more detail below.Thus, exemplary node association manager, when executing in a node,directs how the node associates (e.g., enters an active connection mode)with one or more other nodes with input from the server.

The exemplary node association manager for a node may indicate through aStatus Flag if the node requires an acknowledgement or connection, or ifit has information available for upload to the backend. Thus, while anode may not be associated or actively connected yet to another node, astatus of the node may be inferred from, for example, the statusinformation in the node's broadcast header.

Regarding connections between nodes, there are generally secureconnections and unsecure connections. While an embodiment may allowunsecure connections between one or more sets of nodes, otherembodiments rely upon secure connections or authenticate pairings ofnodes. In one embodiment, for a node to pair with another node, theexemplary node association manager first identifies the nodes to beassociated and transmits an association request to the server. Therequest may include a specific request to pair the nodes and ask for thecorresponding pairing credentials from the server, such as server 100.The server 100 may have staged pairing credentials on particular nodesbased on information indicating the nodes would be within wirelessproximity and future pairing may occur. Visibility to the noderelationship may have been determined through scan-advertising, or3^(rd) party data such as barcode scan information indicating the nodesto be within proximity currently or at a future state.

When connecting or not connecting to exchange information under theexemplary node information exchange modes described above, nodesgenerally operate in a number of states, which make up an exemplaryadvertise cycle for an exemplary ID node. Such an exemplary advertisecycle for a node is further explained below with reference to FIG. 8 andin conjunction and consistent with the server-side association managerin code 525, as discussed in more detail below.

Airborne Mode Program Module

In one embodiment, node control and management code 325 may also includean airborne mode program module (not shown). In another embodiment, theairborne mode program module may be implemented as a part of the nodepower manager program module of code 325. An exemplary airborne modeprogram module generally operates to manage the output power of the IDnode's variable power short-range communication interface 375 when theID node is operating in an aircraft. Operating a wireless device withinan aircraft may, in some circumstances, have an unintentional impact onother electronic systems on the aircraft. In more detail, an embodimentof the airborne mode program module may operate to transition the IDnode from different states or modes depending upon particular operationsand/or operational conditions of the aircraft. For example, an exemplaryairborne mode program module may operate to transition the ID node fromone state or mode (e.g., a normal mode prior to takeoff, a disabled modeduring takeoff, an airborne mode while aloft, a disabled mode duringdescent, and a normal mode after landing) based upon detectedenvironmental conditions (e.g., pressure, altitude) and/or flight detailinformation associated with the aircraft. In this way, an ID node may beallowed to normally operate when onboard an aircraft, be disabled fromoperating at all in some circumstances, and be able to operate in anairplane mode that allows sensing and sensor data capture, but that maylimit transmission of an RF output signal to avoid interference with theaircraft's onboard electronics. Further information related to a methodof managing a wireless device (such as an ID node) in an aircraft isdisclosed in greater detail in U.S. patent application Ser. No.12/761,963 entitled “System and Method for Management of WirelessDevices Aboard an Aircraft,” which is hereby incorporated by reference.

Node Data

As previously noted, volatile memory 320 may also include certain data(e.g., profile data 330, security data 335, association data 340, shareddata 345, sensor data, and the like) generated as the ID node 120 aexecutes instructions as programmed or loaded from memory storage 315.In general, data used on a node, such as an ID node, may be receivedfrom other nodes or generated by the node during operations.

In one embodiment, profile data 330 is a type of data that defines ageneral type of behavior for an ID node, such as a Broadcast Profile(discussed in more detail below). In another embodiment where ID node120 a is a BLE device, profile data 330 may include a Bluetooth®compatible profile related to battery service (exposing the state of abattery within a device), proximity between BLE devices, or messagingbetween BLE devices. Thus, exemplary profile data 330 may exist involatile memory 320 and/or memory storage 315 as a type of data thatdefines parameters of node behavior.

In one embodiment, it may be desired to allow secured pairings of nodes.As will be explained in more detail below, as part of secure pairing ofnodes, a request for pairing credentials is generated and sent to server100. Thus, exemplary security data 335 (e.g., PIN data, securitycertificates, keys, etc.) may exist in volatile memory 320 and/or memorystorage 315 as a type of data associated with providing securedrelationships between nodes, such as the requested security credentials.

Association data, such as association data 340, generally identifies aconnected relationship between nodes. For example, ID node 120 a maybecome associated with the master node 110 a as the ID node 120 a moveswithin range of the master node 110 a and after the server directs thetwo nodes to associate (with authorization). As a result, informationidentifying the relationship between ID node 120 a and master node 110 amay be provided to server 100 and may be provided, as some point, toeach of ID node 120 a and master node 110 a. Thus, exemplary associationdata 340 may exist in volatile memory 320 and/or memory storage 315 as atype of data identifying associations between nodes.

Shared data 345 may exist in volatile memory 320 and/or memory storage315 as a type of data exchanged between nodes. For example, context data(such as environmental data) may be a type of shared data 345.

Sensor data 350 may also exist in volatile memory 320 and/or memorystorage 315 as a type of data recorded and collected from an onboardsensor or from another node. For example, sensor data 350 may includetemperature readings from a temperature sensor onboard an ID node and/orhumidity readings from a humidity sensor in another ID node (e.g., fromanother of the ID nodes within container 210 as shown in FIG. 2).

Thus, an ID node (such as node 120 a shown in FIG. 3) is a lower costwireless node that communicates with other ID nodes and master nodes viaa short-range radio with variable RF characteristics, can be associatedwith other nodes, can broadcast to and scan for other nodes, associatedwith other nodes, and store/exchange information with other nodes.

Master Node

A master node, such as master node 110 a shown in more detail in FIG. 4,shares many ID node features but generally expands upon them in order tofunction as a bridge to the server 100. In general, while an ID node isa type of lower level node in an exemplary wireless node network, amaster node is a type of higher level node. An exemplary master node maybe in a fixed location or otherwise stationary, while other examplemaster nodes may be implemented as movable and mobile devices.

Referring now to FIG. 4, exemplary master node 110 a comprises aprocessing or logic unit 400 coupled to a short-range communicationinterface 480, memory storage 415, volatile memory 420, clock/timer 460,and battery/power interface 470. In some embodiments, the short-rangecommunication interface 480 may have variable power characteristics,such as receiver sensitivity and RF output power level. Those skilled inthe art will appreciate that processing unit 400 is logic, such as amicroprocessor or microcontroller, which generally performs computationson data and executes operational and application program code and otherprogram modules within the master node 110 a.

In general, those skilled in the art will appreciate that thedescription of hardware with respect to ID node 110 a in FIG. 4 appliesto the similar hardware and software features appearing in each type ofnode, including a master node. Those skilled in the art will appreciatethat exemplary master node 110 a is a hardware-based component that mayimplement processor 400 with a single processor or logic unit, a morepowerful multi-core processor, or multiple processors depending upon thedesired implementation. In one embodiment, processing unit 400 may beimplemented with a low power microprocessor and associated peripheralcircuitry. Less complex microcontrollers or discrete circuitry may beused to implement processing unit 400 as well as more complex andsophisticated general purpose or dedicated purpose processors.

In yet another embodiment, exemplary processing unit 400 may beimplemented by a low power ARM1176JZ-F application processor used aspart of a single-board computer, such as the Raspberry Pi Computer ModelB-Rev-2. The ARM application processor is embedded within a Broadcom®BCM2835 system-on-chip (SoC) deployed in the Raspberry Pi Computer. Inthis embodiment, the Raspberry Pi Computer device operates as a core ofexemplary master node 110 a and includes a Secure Digital memory cardslot and flash memory card operating as memory storage 415, a 512 MbyteRAM memory storage operating as volatile memory 420, an operating system(such as Linux) stored on memory storage 415 and running in volatilememory 420, and peripherals that implement clock/timer 460, and a powersupply operating as a power interface 470.

Like short-range interface 375 in ID node 120 a, exemplary master node110 a includes a short-range communication interface 480 as aprogrammable radio and an omni-directional antenna coupled to theprocessing unit 400. In some embodiments, the short-range communicationinterface 480 may have variable RF power characteristics, such asreceiver sensitivity and/or RF output signal power level. In someembodiments, interface 480 may use an antenna with a different antennaprofile when directionality may be desired. Examples of short-rangecommunication interface 480 may include other hardware (not shown) foroperatively coupling the device to a specific short-range communicationpath (e.g., a Bluetooth® Low Energy (BLE) connection path communicatingat 2.4 GHz). While BLE is used in one embodiment to enable a short-rangecommunication protocol, variable power short-range interface 480 may beimplemented with other low power, short-range communication protocols,such as ultra-low power communication protocols used with ultra-widebandimpulse radio communications, ZigBee protocols, IEEE 802.15.4 standardcommunication protocols, and the like.

In one embodiment, various RF characteristics of the radio'stransceiver, such as the RF output power and the RF receiver sensitivitymay be dynamically and programmatically varied under control ofprocessing unit 400. In other embodiments, further RF characteristics ofthe radio's transceiver may be programmatically varied, such asfrequency, duty cycle, timing, modulation schemes, spread spectrumfrequency hopping aspects, etc., as needed to flexibly adjust the RFoutput signal as needed depending upon a desired implementation andanticipated use of exemplary master node 110 a. In other words,embodiments of master node 110 a (or any other master node) may haveprogrammatically adjustable RF characteristics (such as an adjustable RFoutput signal power, an adjustable RF receiver sensitivity, the abilityto switch to a different frequency or frequency band, etc.).

In addition to the short-range communication interface 480, exemplarymaster node 110 a includes a medium and/or long-range communicationinterface 485 to provide a communication path to server 100 via network105. Those skilled in the art will appreciate that in some embodiments,an exemplary communication interface deployed may be considered toembody a short-range communication interface (such as interface 480) ora medium/long range communication interface (such as interface 485).However, in more general embodiments, reference to a communicationinterface may include an interface that collectively implements aplurality of different exemplary data communication interfaces whilestill being generally referenced as “a communication interface” or“wireless communication interface.”

In one embodiment, communication interface 485 may be implemented with amedium range radio in the form of an IEEE 802.11g compliant Wi-Fitransceiver. In another embodiment, communication interface 485 may beimplemented with a longer range radio in the form of a cellular radio.In yet another embodiment, both a Wi-Fi transceiver and a cellular radiomay be used when best available or according to a priority (e.g., firstattempt to use the Wi-Fi transceiver if available due to possible lowercosts; and if not, then rely on the cellular radio). In other words, anembodiment may rely upon the longer range cellular radio part ofinterface 485 as an alternative to the medium range Wi-Fi transceiverradio, or when the medium range radio is out of reach from a connectinginfrastructure radio within network 105. Thus, in these embodiments,medium and/or long-range communication interface 485 may be used tocommunicate captured node information (e.g., profile data 430,association data 440, shared data 445, sensor data 450, and locationdata 455) to server 100.

The battery/power interface 470 for master node 110 a generally powersthe circuitry implementing master node 110 a. In one embodiment,battery/power interface 470 may be a rechargeable power source. Forexample, a master node may have a rechargeable power source along with asolar panel that charges the power source in order to help facilitatedeployment of the master in a remote location. In another embodiment,battery/power interface 470 may be a non-rechargeable power sourceintended to be disposed of after use. In yet another embodiment,battery/power interface 470 may be a power interface connector (such asa power cord and internal power supply on master node 110 a). Thus, whenan exemplary master node is in a fixed or stationary configuration, itmay be powered by a power cord connected to an electrical outlet, whichis coupled to an external power source. However, other mobile masternodes may use an internal power source, such as a battery.

The clock/timer 460 for master node 110 a generally provides one or moretiming circuits used in, for example, time delay, pulse generation, andoscillator applications. In an embodiment where master node 110 aconserves power by entering a sleep or dormant state for a predeterminedtime period as part of overall power conservation techniques,clock/timer 460 assists processing unit 400 in managing timingoperations.

Optionally, an embodiment may also implement master node 110 a asincluding one or more sensors 465 (similar to sensors deployed on IDnode based Sensor nodes and described above with respect to FIG. 3).Additionally, an embodiment of master node 110 a may also provide a userinterface 405 to indicate status and allow basic interaction for reviewof captured node data and interaction with nodes and server 100. In oneembodiment, user interface 405 may provide a display, interactivebuttons or soft keys, and a pointing device to facilitate interactionwith the display. In a further embodiment, a data entry device may alsobe used as part of the user interface 405. In other embodiments, userinterface 405 may take the form of one or more lights (e.g., statuslights), audible input and output devices (e.g., a microphone andspeaker), or touchscreen.

As previously noted, an exemplary master node, such as master node 110a, may be positioned in a known fixed location or, alternatively,includes dedicated location positioning circuitry 475 (e.g., GPScircuitry) to allow the master node self-determine its location or todetermine its location by itself. In other embodiments, alternativecircuitry and techniques may be relied upon for location circuitry 475(rather than GPS), such as location circuitry compatible with othersatellite-based systems (e.g., the European Galileo system, the RussianGLONASS system, the Chinese Compass system), terrestrial radio-basedpositioning systems (e.g., cell phone tower-based or Wi-Fi-basedsystems), infrared positioning systems, visible light based positioningsystems, and ultrasound-based positioning systems).

Regarding memory storage 415 and volatile memory 420, both areoperatively coupled to processing unit 400 in exemplary master node 110a. Both memory components provide program elements used by processingunit 400 and maintain and store data elements accessible to processingunit 400 (similar to the possible data elements stored in memory storage315 and volatile memory 320 for exemplary ID node 120 a).

In the embodiment shown in FIG. 4, memory storage 415 maintains avariety of executable program code (e.g., master control and managementcode 425), data similar to that kept in an ID node's memory storage 315(e.g., profile data 430, security data 435, association data 440, shareddata 445, sensor data 450, and the like) as well as other data morespecific to the operation of master node 110 a (e.g., location data 455that is related to the location of a particular node). Like memorystorage 315, memory storage 415 is a tangible, non-transient computerreadable medium on which information (e.g., executable code/modules,node data, sensor measurements, etc.) may be kept in a non-volatile andnon-transitory manner.

Like volatile memory 320 in ID node 120 a, volatile memory 420 istypically a random access memory (RAM) structure used by processing unit400 during operation of the master node 110 a. Upon power up of masternode 110 a, volatile memory 120 may be populated with an operationalprogram (such as master control and management code 425) or specificprogram modules that help facilitate particular operations of masternode 110 a. And during operation of master 110 a, volatile memory 420may also include certain data (e.g., profile data 430, security data435, association data 440, shared data 445, sensor data 450, and thelike) generated as the master node 110 a executes instructions asprogrammed or loaded from memory storage 415.

Master Control & Management Code

Generally, an embodiment of master control and management code 425 is acollection of software features implemented as programmatic functions orprogram modules that generally control the behavior of a master node,such as master node 110 a. In one embodiment, master control andmanagement code 425 generally comprises several programmatic functionsor program modules including (1) a node advertise and query (scan) logicmanager, which manages how and when a node communicates; (2) aninformation control and exchange manager, which manages whether and howinformation may be exchanged between nodes; (3) a node power manager,which manages power consumption and aspects of RF output signal powerand/or receiver sensitivity for variable short-range communications; (4)an association manager focusing on how the node associates with othernodes; and (5) a location aware/capture module to determine nodelocation.

Master Node Program Modules and ID Node Modules

In an exemplary embodiment, program modules (1)-(4) of master nodecontrol and management code 425 generally align with the functionalityof similarly named program modules (1)-(4) of node control andmanagement code 325 as described above with respect to FIG. 3.Additionally, as node control and management code 325 may also comprisean airborne mode program module, those skilled in the art willappreciate and understand that master node control and management code425 may also comprise a similar functionality airborne mode programmodule in order to allow advantageous operations of a master node whileairborne. However, and consistent with examples set forth below, suchmodules may have some differences when in a master node compared withthose controlling an ID node.

Location Aware/Capture Module

In addition to exemplary program modules (1)-(4) of code 425, anexemplary embodiment of master node control and management code 425 willfurther comprise an exemplary location aware/capture module related tonode location (more generally referred to as a location manager modulefor a master node). In general, the exemplary location aware/capturemodule deployed in an exemplary master node may determine its ownlocation and, in some embodiments, the location of a connected node.Embodiments of the exemplary location aware/capture module may work inconjunction with location manager program code residing and operating ina server (e.g., as part of server control and management code 525) whendetermining node locations of other nodes, as discussed in more detailherein.

In one embodiment, a master node may be positioned in a known, fixedlocation. In such an embodiment, the exemplary location aware/capturemodule may be aware that the master node location is a known, fixedlocation, which may be defined in a fixed, preset, or preprogrammed partof memory storage 415 (e.g., information in the location data 455maintained in memory storage 415). Examples of such location informationmay include conventional location coordinates or other descriptivespecifics that identify the location of the master node. In anotherembodiment where the master node may not be inherently known or a fixedlocation at all times (e.g., for a mobile master node), the exemplarylocation aware/capture module may communicate with location circuitry,such as GPS circuitry 475 on a master node, to determine the currentlocation of the master node.

In an embodiment, the location of the master node may be communicated tothe server, which may use this location information as part of managingand tracking nodes in the wireless node network. For example, if anexemplary master node is mobile and has determined a new currentlocation using location circuitry 475, the master node may provide thatnew current location for the master node to the server. Additionally,when the master node's exemplary location aware/capture moduledetermines the location of a node associated with the master node, themaster node may also provide the location of that node associated withthe master node to the server.

Server

While FIGS. 3 and 4 illustrate details of hardware and software aspectsof an exemplary ID node and exemplary master node, respectively, FIG. 5provides a more detailed diagram of an exemplary server that may operateas part of an exemplary wireless node network in accordance with anembodiment of the invention. In an exemplary embodiment, server 100 maybe referred to as an Association and Data Management Server (ADMS) thatmanages the nodes, collects information from the nodes, stores thecollected information from the nodes, maintains or has access to contextdata related to the environment in which the nodes are operating, andmay provide information about the nodes (e.g., status, sensorinformation, etc.) to requesting entities. Further details on variousembodiments that take advantage of this functionality are explainedbelow. Those skilled in the art will appreciate that node density,geographic installation characterization, and network connectively areall types of examples of factors that may impact a final architecturedesired for an embodiment of a wireless node network.

Referring now to FIG. 5, exemplary server 100 is shown as a networkedcomputing platform capable of connecting to and interacting with atleast the wireless master nodes. In other embodiments, exemplary server100 is also capable of connecting to and interacting with one or moreuser access devices. Those skilled in the art will appreciate thatexemplary server 100 is a hardware-based component that may beimplemented in a wide variety of ways. For example, server 100 may use asingle processor or may be implemented as one or more part of amulti-processor component that communicates with devices (such as useraccess devices 200, 205) and wireless nodes (such as master node 110 a).

In general, those skilled in the art will further appreciate that server100 may be implemented as a single computing system, a distributedserver (e.g., separate servers for separate server related tasks), ahierarchical server (e.g., a server implemented with multiple levelswhere information may be maintained at different levels and tasksperformed at different levels depending on implementation), or a serverfarm that logically allows multiple distinct components to function asone server computing platform device from the perspective of a clientdevice (e.g., devices 200, 205 or master node 110 a). In some regionaldeployments, an exemplary server may include servers dedicated forspecific geographic regions as information collected within differentregions may include and be subject to different regulatory controls andrequirements implemented on respective regional servers.

Likewise, while the embodiment shown in FIG. 5 illustrates a singlememory storage 515, exemplary server 100 may deploy more than one memorystorage media. And memory storage media may be in differingnon-transitory forms (e.g., conventional hard disk drives, solid statememory such as flash memory, optical drives, RAID systems, cloud storageconfigured memory, network storage appliances, etc.).

At its core, exemplary server 100 shown in FIG. 5 comprises a processingor logic unit 500 coupled to a network interface 590, which facilitatesand enables operative connections and communications through network 105with one or more master nodes as well as, in some embodiments, useraccess devices, such as devices 200, 205. In one embodiment, server 100may include a medium and/or long-range communication interface 595 withwhich to more directly communicate with one or more master nodes. Usingthese communication paths as well as program code or program modules(such as server control and management code 525), the server 100generally operates to coordinate and manage information related to an IDnode as an item associated with the ID node physically moves from onelocation to another.

As a computing platform, the processing unit 500 of exemplary server 100is operatively coupled to memory storage 515 and volatile memory 520,which collectively store and provide a variety of executable programcode (e.g., server control and management code 525), data similar tothat kept in a master or ID node's respective memory storage (e.g.,profile data 530, security data 535, association data 540, shared data545, sensor data 550, location data 555) and context data 560 related tothe environment in which the nodes are operating (e.g., informationgenerated from within the wireless node network and information createdexternal to the wireless node network).

Like memory storage 315 and storage 415, memory storage 515 is atangible, non-transient computer readable medium on which information(e.g., executable code/modules (e.g., server control and management code525), node-related data (e.g., profile data 530, security data 535,association data 540, location data 555, etc.), measurement information(e.g., a type of shared data 545, sensor data 550, etc.), andinformation on the contextual environment for the nodes (e.g., contextdata 560) may be kept in a non-volatile and non-transitory manner.

Those skilled in the art will appreciate that the above identificationof particular program code and data are not exhaustive and thatembodiments may include further executable program code or modules aswell as other data relevant to operations of a processing-based device,such as an ID node, a master node, and a server.

Context Data

As noted above, server 100 may access context data 560 as part ofmanaging nodes in the wireless node network. The exemplary server 100may contain a collection of such context data 560 in a context database565 according to an embodiment. As illustrated in FIG. 5, exemplarycontext database 565 is a single database accessible by processing unit500 internal to server 100. Those skilled in the art will readilyunderstand that other configurations that provide an accessiblecollection of context data 560 are possible and contemplated within thescope and principles of embodiments of the invention. For example,context database 565 may be an externally accessible database (ormultiple databases), such as an accessible storage maintained outsidethe server 100 via a dedicated interface or a network storage device (ornetwork attached storage (NAS) unit). In yet another embodiment, thecontext database may be separately maintained by an external databaseserver (not shown) that is distinct from server 100, but accessiblethrough a communication path from server 100 to a separate databaseserver (e.g., via network 105). Furthermore, those skilled in the artwill appreciate that context database 565 may be implemented with cloudtechnology that essentially provides a distributed networked storage ofcollections of information (such as context data 560, sensor data 550,shared data 545, etc.) accessible to server 100.

Within context database 565, an exemplary embodiment of the collectionof context data 560 may be maintained that generally relates to anenvironment in which the nodes are operating or anticipated to beoperating. In more detail, the context data 560 may generally relate towhat a similar node has experienced in a similar environment to what agiven node is presently experiencing or is anticipated to experience asthe given node moves.

In a general example, an environment in which a node may be actually oranticipated to be operating may include different types ofenvironments—for example, an electronic communication environment (e.g.,an RF environment that may be cluttered with signals or includematerials or structure that may impede or otherwise shield RFcommunications), a physical environment of an anticipated path alongwith the identified node moves (e.g., temperature, humidity, security,and other physical characteristics), a conveyance environment related tohow a node may move or be anticipated to be moving (e.g., speed andother parameters of a truck, airplane, conveyor system), and a densityenvironment related to the density of nodes within an area near aparticular node (e.g., how many nodes are anticipated to occupy acorridor, such as structure 2200 shown in FIG. 22A, or a storagefacility through which a particular ID node is anticipated to transit onits shipping path).

In light of these different aspects of a node's operating environment,exemplary context data 560 may provide information related to differentstructures and conditions related to movement of an item (e.g., aparticular type of courier device, vehicle, facility, transportationcontainer, etc.). Such information may be generated by an entityoperating the wireless node network, such as a shipping company.Additionally, exemplary context data 560 may include third party datagenerated external to the wireless node network. Thus, context data,such as data 560, may include a wide variety of data that generallyrelates to the environment in which the nodes are operating and may beused to advantageously provide enhanced node management capabilities inaccordance with embodiments of the present invention.

In general, FIG. 5 illustrates exemplary types of context data 560 beingmaintained in database 565 and in volatile memory 520. Those skilled inthe art will appreciate that context data 560 may also be maintained inother data structures, in addition to or instead of maintaining suchinformation in a database. As illustrated in FIG. 5, exemplary types ofcontext data 560 may include but are not limited to scan data 570,historic data 575, shipment data 580, layout data 585, RF data 587, and3^(rd) party data.

Scan data 570 is generally data collected for a particular item relatedto an event. For example, when an item is placed in a package (such aspackage 130), a label may be generated and placed on the exterior of thepackage. The label may include a visual identifier that, when scanned byan appropriate scanning device capable of capturing, identifies thepackage. The information generated in response to scanning theidentifier (a type of event), may be considered a type of scan data.Other scan data 570 may include, for example, general inventory datagenerated upon manual entry of information related to the package;captured package custodial control data; and bar code scan data.

Historic data 575 is generally data previously collected and/or analyzedrelated to a common characteristic. Historic data 575 embodiesoperational knowledge and know-how for a particular characteristicrelevant to operations of the wireless node network. For example, thecommon characteristic may be a particular event (e.g., movement of anitem from an open air environment to within a particular closedenvironment, such as a building), a type of item (e.g., a type ofpackage, a type of content being shipped, a location, a shipment path,etc.), a success rate with a particular item (e.g., successfulshipment), and the like. Another example of historic data 575 mayinclude processing information associated with how an item has beenhistorically processed as it is moved from one location to another(e.g., when moving within a particular facility, processing informationmay indicate the item is on a particular conveyor and may includeinformation about the conveyor (such as speed and how long it isanticipated the item will be on the conveyor)).

Shipment data 580 is generally data related to an item being moved fromone location to another location. In one embodiment, shipment data 580may comprise a tracking number, content information for an item beingshipped, address information related to an origin and destinationlocations, and other characteristics of the item being moved.

Layout data 585 is generally data related to the physical area of one ormore parts of an anticipated path. For example, an embodiment of layoutdata 585 may include building schematics and physical dimensions ofportions of a building in which a node may be transiting. An embodimentmay further include density information associated with physical areasto be transited and anticipated numbers of potential nodes in thoseareas as types of layout data. In another example, an embodiment oflayout data may include a configuration of how a group of packages maybe assembled on a pallet, placed into a shipping container (e.g., a unitload device (ULD)) that helps move a collection of items on variousforms with single mode or intermodal transport.

RF data 587 is generally signal degradation information about a signalpath environment for a particular type of node and may relate toparticular adverse RF conditions that may cause signal fluctuations,interference, or other degradation from the otherwise optimal signalpath environment for that type of node. For example, RF data may includeshielding effects when using a particular packaging or location,shielding effects when the package is within a particular type ofcontainer or assembled as part of a palletized shipment, shieldingeffects when particular content is shipped, and other physical andelectronic interference factors.

Third party data 589 is an additional type of context data 560 thatgenerally includes data generated outside the network. For example,third party data may include weather information associated withparticular areas to be transited as the item is moved along ananticipated path from one location to another. Those skilled in the artwill appreciate other types of third party data that relate to physicaland environmental conditions to be faced by an item being moved from onelocation to another may also be considered context data 560.

The use of context data, such as context data 560 described above,advantageously helps server 100 better manage movement of items, providebetter location determination, enhance intelligent operation andmanagement of different levels of the wireless node network, and provideenhanced visibility to the current location and status of the itemduring operation of the wireless node network. In one embodiment, servercontrol and management code 525 may provide such functionality thatenables the wireless node network to be contextually aware andresponsive.

Server Control & Management Code

Generally, server control and management code 525 controls operations ofexemplary server 100. In an embodiment, server control and managementcode 525 is a collection of software features implemented asprogrammatic functions in code or separate program modules thatgenerally control the behavior of server 100. Thus, exemplary servercontrol and management code 525 may be implemented with severalprogrammatic functions or program modules including, but not limited to,(1) a server-side association manager, which provides a framework formore robust and intelligent management of nodes in the wireless nodenetwork; (2) a context-based node manager, which enhances management ofnodes in the wireless node network based upon context data; (3) asecurity manager, which manages secure pairing aspects of nodemanagement; (4) a node update manager, which provides updated ordifferent programming for a particular node and shares information withnodes; (5) a location manager for determining and tracking the locationof nodes in the network; and (6) an information update manager, whichservices requests for information related to the current status of anode or generally providing information about a node or collected from anode.

Server-Side Association Manager

The server-side association manager (also referred to as a server-sideassociation management function) is generally a program module inexemplary code 525 that is responsible for intelligently managing thenodes in the wireless node network using a secure information framework.In an embodiment, this framework may be implemented to be acontext-driven, learning sensor platform. The framework may also enablea way for information (such as RF scan, location, date/time, and sensordata) to be securely shared across nodes, a way to change the behaviorof a node, and for a node to know it is considered “missing.” Theframework established during operation of the server-side associationmanager allows the network of nodes to be managed as a system withenhanced and optimized accuracy of determining the physical location ofeach ID Node. Further information regarding particular embodiments ofsuch an association management framework and methods are explained belowin more detail.

Context-Based Association Manager

The context-based node manager is generally a program module inexemplary code 525 that is responsible for incorporating context data aspart of management operations to provide an enhanced data foundationupon which visibility of the nodes may be provided. In some embodiments,the context-based node manager may be implemented as part of theserver-side association manager while other embodiments may implementthe context-based node manager as a separate program module.

In one embodiment, the enhanced data foundation relies upon contextdata, such as context data 560 (e.g., scan data 570, historic data 575,shipment data 580, layout data 585, and other third party contextualdata providing information regarding the conditions and environmentsurrounding an item and ID node moving from one location to another.Such context data (e.g., the network know-how, building layouts, andoperational knowledge of nodes and shipping paths used with the wirelessnode network) may provide the enhanced building blocks that allow theserver 100 to manage tracking and locating of nodes in a robustlyenriched contextual environment. In an embodiment, context-basedmanagement provides visibility to the system through data analysis forwhen and how associations should be expected as the nodes travel throughthe wireless node network. In other embodiments, it may provide thefoundation for better understanding RF signal degradation, which can becaused by the operating environment, packaging, package content, and/orother packages related to an item and its ID node.

Security Manager

The security manager module, which may be implemented separately or aspart of the association manager module in exemplary server control andmanagement code 525, helps with associating two nodes in the wirelessnode network by managing aspects of secure pairing of the nodes. In oneembodiment, security manager module provides the appropriate pairingcredentials to allow a node to securely connect to another node. Thus,when a node desires to connect to another node, an embodiment requiresappropriate pairing credentials be generated by the server, provided tothe nodes, and observed within the nodes to allow for a successfulconnection or association of nodes.

In operation, a node (such as master node 110 a) identifies the addressof the node (such as ID node 120 a) to whom it desires to connect. Withthis address, the node prepares a pairing request and sends the requestto the server 110. The server 100 operates under the control of thesecurity manager module of the association manager, and determineswhether the requesting node should be connected or otherwise associatedwith the other node. If not, the server does not issue the requestedsecurity credentials. If so and in accordance with the desiredassociation management paradigm set by the association manager of code525, server provides the requested credentials necessary for asuccessful wireless pairing and the establishment of securecommunications between the associated nodes.

Node Update Manager

The exemplary server control and management code 525 may include a nodeupdate manager module that provides updated programming information tonodes within the wireless node network and collects information fromsuch nodes (e.g., shared data 545, sensor data 550). The node updatemodule may be implemented separately or as part of the associationmanager module in exemplary server control and management code 525.

Providing an update to a node's programming may facilitate and enabledistribution of node functions to save power and better manage the nodesas a system. For example, one embodiment may alter the functionalresponsibility of different nodes depending on the context orassociation situation by temporarily offloading responsibility for aparticular function from one node to another node. Typically, the serverdirects other nodes to change functional responsibility. However, insome embodiments, a master node may direct other nodes to alterfunctional responsibility.

Sharing information between nodes and with server (e.g., via anexemplary node update manager) facilitates collecting information from anode and sharing information with other nodes as part of an associationmanagement function of server 100. For example, one embodiment maycollect and share RF scan data (a type of shared data 545), informationabout a node's location (a type of location data 555), systeminformation about date/time (another type of shared data 545), andsensor measurements collected from sensor nodes (a type of sensor data550).

Location Manager

The exemplary server control and management code 525 may include alocation manager module that helps determine and track node locations.In a general embodiment, the location of a node may be determined by thenode itself (e.g., a master node's ability to determine its own locationvia location circuitry 475), by a node associated with that node (e.g.,where a master node may determine the location of an ID node), by theserver itself (e.g., using location information determined by one ormore techniques implemented as part of code 525), and by a combinedeffort of a master node and the server.

In general, an exemplary ID node may be directly or indirectly dependenton a master node to determine its actual physical location. Embodimentsmay use one or more methodologies to determine node location. Forexample and as more specifically described below, possible methods fordetermining node location may relate to controlling an RF characteristicof a node (e.g., an RF output signal level and/or RF receiversensitivity level), determining relative proximity, consideringassociation information, considering location adjustments for contextinformation and an RF environment, chaining triangulation, as well ashierarchical and adaptive methods that combine various locationmethodologies. Further information and examples of how an exemplarylocation manager module may determine a node's location in accordancewith such exemplary techniques are provided in more detail below.

Additionally, those skilled in the art will appreciate that it may alsobe possible to determine what constitutes an actionable location versusactual location based upon contextual information about the item beingtracked. For example, a larger item may require relatively less locationaccuracy than a small item such that operational decisions and statusupdates may be easier implemented with knowledge of context. If the sizeof the item is known, the location accuracy can be tuned accordingly.Thus, if a larger item is to be tracked, or if the system's contextualawareness of it is such that lower location accuracy can be used, astronger signal and thus wider area of scanning may be employed, whichmay help in situations where RF interference or shielding is an issue.

Information Update Manager

The exemplary server control and management code 525 may include aninformation update manager module that provides information related tooperations of the wireless node network and status of nodes. Suchinformation may be provided in response to a request from a deviceoutside the wireless node network (such as user access device 200). Forexample, someone shipping an item may inquire about the current statusof the item via their laptop or smartphone (types of user accessdevices), which would connect to server 100 and request suchinformation. In response, the information update manager module mayservice such a request by determining which node is associated with theitem, gathering status information related to the item (e.g., locationdata, etc.), and provide the requested information in a form that istargeted, timely, and useful to the inquiring entity.

In another example, a user access device may connect to server 100 andrequest particular sensor data from a particular node. In response,information update manager may coordinate with node update manager, andprovide the gathered sensor data 545 as requested to the user accessdevice.

Node Filtering Manager

An embodiment of exemplary server control and management code 525 mayoptionally comprise a node filtering manager, which helps manage thetraffic of nodes with a multi-level filtering mechanism. The filteringessentially sets up rules that limit potential associations andcommunications. An example of such a node filtering management maydefine different levels or modes of filtering for a master node (e.g.,which ID nodes can be managed by a master node as a way of limiting thecommunication and management burdens on a master node).

In one example, a “local” mode may be defined where the ID node onlycommunicates and is managed by the assigned master node at the locationwhere the last wireless node contact back to server 100 and/or wherethird party data indicates the assigned master node and ID node are inphysical and wireless proximity. Thus, for the “local” mode of trafficfiltering, only the assigned master node communicates and processesinformation from a proximately close and assigned ID node.

Moving up to a less restrictive filtering mode, a “regional” mode offiltering may be defined where the ID node may communicate and bemanaged by any master node at the location last reported back to server100 and/or where third party data indicates the ID node is located.Thus, for the “regional” mode of traffic filtering, any master node nearthe ID node may communicate and process information from that ID node.This may be useful, for example, when desiring to implement a limit onassociations and pairings to within a particular facility.

At the least restrictive filtering mode, a “global” mode of filteringmay be defined as essentially system-wide communication where the IDnode may be allowed to communicate and be managed by any master node. Inother words, the “global” mode of traffic filtering allows any ID nodewithin the wireless node network to communicate information through aparticular master node near the ID node may communicate and processinformation from that ID node.

Thus, with such exemplary filtering modes, an ID node in a certaincondition (e.g., distress, adverse environmental conditions, adverseconditions of the node, etc.) may signal the need to bypass anyfiltering mechanism in place that helps manage communications andassociation by using the “Alert” Status Flag. In such an example, thiswould operate to override any filtering rules set at the Master Nodelevel in order to allow an ID node to be “found” and connect to anothernode.

Thus, exemplary server 100 is operative, when executing code 525 andhaving access to the types of data described above, to manage the nodes,collect information from the nodes, store the collected information fromthe nodes, maintain or have access to context data related to theenvironment in which the nodes are operating, and provide informationabout the nodes (e.g., status, sensor information, etc.) to a requestingentity.

Node Communication & Association Examples

To better illustrate how exemplary management and communicationprinciples may be implemented within an exemplary wireless node network,FIGS. 8-12 provide several examples of how exemplary components of thewireless node network may generally communicate (advertising &scanning), associate, and exchange information during different types ofoperations in various embodiments. FIGS. 22A-C also provide a moredetailed application of such exemplary association and communicationactivities when an exemplary ID node moves along a transit path (e.g.,through a corridor) and is tracked and managed by different master nodesand a server in an embodiment.

Node Advertising Cycle Example

As generally explained above, a node may have several different types ofadvertising states in which the node may be connectable with other nodesand may communicate with other nodes. And as a node moves within awireless node network, the node's state of advertising and connectionmay change as the node disassociates with a previously connected node,associates with a new node, or finds itself not associated with othernodes. In some situations, a node may be fine and in normal operationnot be connected or associated with another node. However, in othersituations, a node may raise an issue with potentially being lost if ithas not connected with any other node in a very long period of time. Assuch, a node may go through different types of advertising states inthese different operational situations.

Generally, a node may be in a state where it is not connectable withother nodes for a certain period of time (also referred to as anon-connectable interval). But later, in another state, the node maywant to be connected and advertises as such for a defined connectableperiod (also referred to as a connectable interval). As the nodeadvertises to be connected, the node may expect to be connected at somepoint. In other words, there may be a selectable time period withinwhich a node expects to be connected to another node. However, if thenode is not connected to another node within that period of time(referred to as an Alert Interval), the node may need to take specificor urgent action depending upon the circumstances. For example, if anode has not been connected to another node for 30 minutes (e.g., anexample alert interval), the node may change operation internally tolook “harder” for other nodes with which to connect. More specifically,the node may change its status flag from an Alert Level 0 (no issue,operating normal) to Alert Level 2 in order to request that anyavailable master node acknowledge receipt of the advertisement packetbroadcasted by the node seeking a connection.

FIG. 8 is a diagram illustrating exemplary advertising states (orinformation exchange and node connectability states) and factorsinvolved in transitions between the states by an exemplary ID node in awireless node network in accordance with an embodiment of the invention.Referring now to FIG. 8, three exemplary states for a node areillustrated as part of an exemplary advertising cycle for thenode—namely, an ID Node Non-Connectable Advertising state 805, an IDNode Discoverable Advertising state 815, and an ID Node GeneralAdvertising state 830. Transitions between these states will depend onfactors related to expirations of the types of intervals describedabove. In an embodiment, the duration of each of these intervals willdepend upon the system implementation and the contextual environmentwithin which the ID node is operating. Such time intervals may, forexample, be set by server 100 as part of data (e.g., profile data,association data, context data) provided to the node when updating thenode and managing operations of the node.

Referring to the example illustrated in FIG. 8, an exemplary ID node mayhave an alert interval set at, for example, 30 minutes, and be in IDNode Non-Connectable Advertising state 805 with a non-connectableinterval set at 5 minutes. In state 805, the ID node may broadcast oradvertise, but is not connectable and will not receive a SCAN_REQmessage (a type of request for more information sent to the advertisingnode from another node). Thus, the ID node in state 805 in this examplemay advertise in a non-connectable manner for at least 5 minutes butexpects to be connected within 30 minutes.

If the alert interval has not yet elapsed (factor 810) and thenon-connectable interval is still running (factor 825), the ID nodesimply stays in state 805. However, if the alert interval has notelapsed (factor 810) and the non-connectable interval elapses (factor825), the ID node will enter a mode where it wants to try to connect toanother node for a period of time (e.g., a 1 minute connectableinterval) and will move to the ID Node General Advertising state 830 inthe exemplary advertising cycle of FIG. 8. In state 830, as long as theconnectable interval is running, the ID node will stay in this statewhere it is connectable to another node and will receive SCAN_REQ typesof requests from other nodes in response to the advertising packets theID node is broadcasting. However, when the connectable interval (e.g.,the 1 min period) elapses or expires (factor 835), the ID node returnsback to the Non-connectable Advertising state 805 for either the nexttime the non-connectable interval elapses (and the ID node again triesto connect in state 830) or the alert interval finally elapses (and theID node finds itself in a situation where it has not connected toanother node despite its efforts to connect in state 830).

When the alert interval finally elapses (factor 810), the ID node movesto the ID Node Discoverable Advertising state 815. Here, the ID node isnot yet connectable but will receive a SCAN_REQ type of request fromother nodes in response to advertising packets the ID node isbroadcasting. In this state 815, the exemplary ID node may alter itsstatus flag to indicate and reflect that its alert interval has expiredand that the node is now no longer in normal operation. In other words,the ID node may change the status flag to a type of alert status beingbroadcasted to indicate the ID node urgently needs to connect withanother node. For example, the status flag of the advertising packetbroadcast by the ID node may be changed to one of the higher AlertLevels depending on whether the node needs to upload data (e.g., AlertLevel 3 status) or synchronize timer or other data with another node(e.g., Synchronize status). With this change in status flag, and the IDnode in state 815 broadcasting, the ID node awaits to receive a requestfrom another node that has received the broadcast and requested moreinformation via a SCAN_REQ message (factor 820) sent to the ID node fromthat other node. Once a SCAN_REQ message has been received by the IDnode (factor 820), the ID node that went into the alert mode because ithad not connected with another node within the alert interval canconnect with that other node, upload or share data as needed, and thenshift back to state 805 and restart the alert interval andnon-connectable intervals.

Master Node to ID Node Association Example

Advertising (broadcasting) and scanning (listening) are ways nodes maycommunicate during association operations. FIGS. 9-12 provide examplesof how network elements of a wireless node network (e.g., ID nodes,master nodes, and a server) may communicate and operate when connectingand associating as part of several exemplary wireless node networkoperations.

FIG. 9 is a diagram illustrating exemplary components of a wireless nodenetwork during an exemplary master-to-ID node association in accordancewith an embodiment. Referring now to FIG. 9, exemplary master node M1910 a is illustrated within communication range of exemplary ID node A920 a. Master node M1 910 a also has a communication path back to server900. As shown, master node M1 910 a is in a scanning or listening mode(e.g., indicated by the “M1 _(scan)” label) while ID node A 920 a is inan advertising or broadcasting mode (e.g., indicated by the “A_(adv)”label). In this example, M1 master node 910 a has captured the addressof ID node A 920 a through A's advertising of at least one advertisingdata packet, and has reported it to the server 900. In this manner, thecapturing and reporting operations effectively create a “passive”association between the nodes and proximity-based custodial control.Such an association may be recorded in the server, such as server 900,as part of association data, such as association data 540.

In another embodiment, passive association between a master node and IDnode may be extended to an “active” association or connection. Forexample, with reference to the embodiment shown in FIG. 9, server 900may instruct master node M1 910 a to associate, connect, or otherwisepair with ID node A 920 a, and forwards the required securityinformation (e.g., PIN credentials, security certificates, keys) tomaster node M1 910 a. Depending on the advertising state of ID node A920 a, ID node A 910 a may only be visible (discoverable) but notconnectable. In such a situation, the master node M1 910 a must waituntil ID node A 920 a is in a connectable state (e.g., the ID NodeGeneral Advertising state) and can be paired. As discussed above withreference to FIG. 8, each ID node has a certain time window during eachtime period where it can be paired or connected.

In this example, when the ID node A 920 a is successfully paired withmaster node M1 910 a, ID node A 920 a may no longer advertise itsaddress. By default, only an unassociated device will advertise itsaddress. A paired or associated node will only advertise its address ifinstructed to do so.

ID Node to ID Node Association Example

In various embodiments, an ID node may associate with or connect toother ID nodes. FIG. 10 is a diagram illustrating exemplary componentsof a wireless node network during an exemplary ID-to-ID node associationin accordance with an embodiment of the invention. Referring now to FIG.10, exemplary master node M1 910 a, ID node A 920 a, and server 900 aresimilarly disposed as shown in FIG. 9, but with the addition of ID nodeB 920 b, which is within communication range of ID node A 920 a. In thisexample, ID node A 920 a is running in query (scan) mode (e.g.,A_(scan)) listening for ID node B 920 b. When ID node A 910 a detects IDnode B 920 b advertising (e.g., B_(adv)) with one or more advertisingdata packets as part of an advertised message from ID node B 920 b, IDnode A 920 a identifies a status flag from the message indicating IDnode B 920 b has, for example, data (e.g., sensor data 350) for upload.As a result, ID node A 920 a logs the scan result (e.g., as a type ofassociation data 340) and, when next connected to master node M1 910 a,ID node A 920 a uploads the captured scan log information to the server900. In this manner, the ID node scanning, capturing, and reportingoperations effectively create a “passive” association between thedifferent ID nodes. Such a passive association may be recorded in theserver 900 as part of association data 540.

In another embodiment, passive association between two ID nodes may beextended to an “active” association or connection. For example, withreference to the embodiment shown in FIG. 10, based upon the capturedstatus flag and uploaded information about ID node B 920 b under thatmode, the server 900 may issue a request to ID node A 920 a throughmaster node M1 910 a to actively connect or pair with ID node B 920 bfor the purpose of downloading information from ID node B 920 b. In oneexample, security credentials that authorize the active connectionbetween ID node A 920 a and ID node B 920 b are downloaded to ID node A920 a from master node M1 910 a, which received them from server 900. Inanother example, the requisite security credentials may have beenpre-staged at ID node A 920 a. And rather than rely upon an ID node toID node connection, master node M1 may have connected directly with IDnode B 920 b if M1 was within communication range of ID node B 920 b.

Information Query ID Node to Master Node Example

An exemplary ID Node may also issue queries to other nodes, both masternodes and ID nodes. FIG. 11 is a diagram illustrating exemplarycomponents of a wireless node network during an exemplary ID-to-masternode query in accordance with an embodiment of the invention. Referringnow to FIG. 11, a similar group of nodes as shown in FIG. 9 appears,except that exemplary master node M1 910 a is in an advertising orbroadcasting mode (e.g., M1 _(adv)) while ID node A 920 a is in ascanning mode (e.g., A_(scan)). In this configuration, ID node A 920 amay query master node M1 910 a for information. In one embodiment, thequery may be initiated through the ID node setting its status flag. Therequested information may be information to be shared, such as a currenttime, location, or environmental information held by the master node M1910 a.

In a passive association example, ID node A 920 a in A_(scan) mode mayhave captured the address of master node M1 910 a. However, since an IDnode cannot directly connect to the server 900 to request pairingsecurity credentials (e.g., security pin information that authorizes anactive connection between ID node A 920 a and master node M1 910 a), apassive association and corresponding pairing will have been initiatedfrom the master node. In another example, it may be possible for ID nodeA 920 a to have the pairing credentials stored as security data 335 froma previous connection. This would allow ID node A 920 a then to initiatethe active association with master node M1 910 a after a passiveassociation.

Alert Level Advertising Example

As previously noted, a node may enter an alert stage or level in one ormore embodiments. For example, if a node has not received anacknowledgement from a master node for an advertising packet within aset period (e.g., an Alert Interval as described in some embodiments),the node will enter a particular alert stage for more specializedadvertising so that it may be “found” or pass along information. FIG. 12is a diagram illustrating exemplary components of a wireless nodenetwork during an exemplary alert advertising mode in accordance with anembodiment of the invention. Referring now to FIG. 12, a similar groupof nodes as shown in FIG. 9 appears, with the addition of another masternode (master node M2 910 b) and another ID node (ID node B 920 b).Exemplary ID node A 920 a is in an advertising or broadcasting mode(e.g., A_(adv)) while nodes M1, M2, and B are each in scanning mode(e.g., M1 _(scan), M2 _(scan), and B_(scan)). In this example andconfiguration as shown in FIG. 12, the status flag in an advertisingmessage from ID node A 920 a has been set to a particular alert level(e.g., Alert Level 2) in the header of the message, requesting anynearby master node to acknowledge it. In one example, this mode may beentered if ID node A 920 a has not connected with another node for a setperiod or time. In another example, ID node A 920 a may enter thisspecialized advertising mode upon received instructions (e.g., fromserver 900 or another nearby node) or a triggered condition (other thantime), such as when a sensor input (such as light) is detected orotherwise registered and the node issues continuous updates of itsaddress as a security feature. The ID node A 920 a set at this alertlevel and in this specialized advertising mode is thus set in an activepairing mode, waiting for pairing credentials.

From a passive association perspective, any node in scanning mode canpassively associate with such an advertising node (e.g., ID node A 920 ain this alert mode). Thus, in an embodiment, the Alert Level 2 statusflag in the advertising header broadcast by ID node A 920 a indicatesthat urgent and active intervention is requested, rather than merelypassively associate without an active connection.

From an active association perspective, any node that uploads thespecial advertising header of ID node A 920 a may be forwarded thesecurity credentials from the server 900. This would allow for the nodereceiving such credentials to actively associate or pair with ID node A920 a.

While FIG. 8 provides examples of how a node may advertise, and FIGS.9-12 provide examples of how different exemplary devices (e.g., IDnodes, master nodes, and a server) may advertise and associate indifferent ways, FIGS. 22A-C provide a progressive set of illustrationsthat expand upon how associating and disassociating may be appliedwithin an exemplary wireless node network. More specifically, FIGS.22A-C show how associations and disassociations may occur when anexemplary ID node is tracked and managed by a server and differentmaster nodes as the ID node moves through an exemplary transit path inaccordance with an exemplary embodiment of the invention.

Referring now to FIG. 22A, a structure 2200 is shown having an entry andexit point. In one example, the structure 2200 may be a corridor oranother part of a building or facility. In another example, structure2200 may be a conveyor system that transports an item and its ID nodefrom the entry point to the exit point. Master node M1 2210 a is locatednear the entry point of structure 2200 while master node M2 2210 b islocated near the exit point. Those skilled in the art will appreciatethat other master nodes may be disposed at additional points instructure 2200, but are not shown for sake of convenience and tosimplify the association hand-off explanation that follows. Server 100is operatively connected to each of master node M1 2210 a and masternode M2 2210 b via network 105.

In one embodiment, server 100 has access to context data 560 related tothe structure 2200, such as layout data 585 on dimensions and materialsmaking up structure 2200. Context data 560 may include historic data 575on how an ID node has operated and successfully been tracked as ittraverses structure 2200 from the entry point to the exist point. Forexample, server 100 may have context data indicating structure 2200 is aconveyor that can transport an item and its ID node from the entry pointto the exit point over a distance of 800 feet. The context data mayfurther indicate typical items are moved at a certain speed on theconveyor of structure 2200 and a nominal time from the entry point tothe exit point may be about 5 minutes. Thus, the server 100 has accessto context data about the environment within with an ID node isoperating and may leverage this to better and more accurately manage theID node.

In FIG. 22A, ID node A 2220 a is shown entering the structure 2200 atthe entry point. Here, ID node A 2220 a may be advertising in hopes ofconnecting with a master node as it enters structure 2200 with, forexample, a non-connectable interval of 10 seconds with a connectableinterval of 5 seconds. In this example, the server 100 knows that IDnode A 2220 a is located near the entry point and anticipates that IDnode A 2220 a should be coming near to master node M1 2210 a at theentry point. Thus, server 100 may set the connectable andnon-connectable intervals accordingly so as to provide a sufficientopportunity for ID node A 2220 a to connect to the next master nodealong the predicted path of the ID node and in accordance with the speedof travel.

Additionally, server 100 may set the alert interval to 1 minute in thiscontext. Here, if ID node A 2220 a is not connected to another nodewithin 1 minute, ID node A 2220 a may broadcast or advertise with amessage having a changed status flag that indicates an alert status sothat ID node A 2220 a can connect to a broader range of other nodes thatsee it is urgent for ID node A 2220 a to connect and, essentially, befound. Depending on the context (e.g., the type of conveyor, the speedof the conveyor, the density of nodes near the entry point, etc.), thoseskilled in the art will appreciate that the server 100 can adjust theadvertising cycle intervals to better accommodate the ID node's currentenvironment.

When master node M1 2210 a is scanning (listening), it may initiallydetect an advertising packet from ID node A 2220 a during node A'snon-connectable interval. But when ID node A 2220 a changes advertisingstates and broadcasts as a connectable node in the general advertisingstate (i.e., during the connectable interval), master node M1 2210 a mayrespond with a SCAN_REQ that acknowledge receipt of the broadcastedmessage and asks for further information from ID node A 2220 a. Masternode M1 2210 a receives the requested information from ID node A 2220 a,and then communicates with the server 100 to notify the server of itspassive association with ID node A 2220 a. Server 100 determines ifactive association is desired, and may authorize the active associationbetween master node M1 2210 a and ID node A 2220 a by sending securitycredentials to master node M1 2210 a, which allow the nodes to securelyconnect and share information. And master node M1 2210 a may determinethe location of ID node A 2220 a (or server 100 may do so by directingmaster node M1 and/or ID node A), and provide the location of ID node A2220 a to server 100. Thus, server 100 is able to manage and track thelocation of ID node A 2220 a as it enters structure 2220 via at leastassociation.

In FIG. 22B, ID node A 2220 a has traversed down part of the transitpath through structure 2200 while remaining associated with master nodeM1 2210 a. However, at some point master node M1 2210 a and ID node A2220 a are disassociated at the direction of server 100 (or when theycan no longer communicate). In one example where ID node A 2220 a is onthe conveyor within structure 2200, server 100 may instruct ID node A2220 a to go to a low power mode for a particular period of time inorder to, for example, conserve ID node power. In another example, thelow power mode may also provide better location accuracy. As the server100 has access to the context data, the server 100 may know that ID nodeA 2220 a was associated with master node M1 2210 a near the entry pointat a given time, and determine that ID node A 2220 a will not be nearthe exit point until the end of the particular period of time. With theID node A 2220 a programmed this way, once the particular periodelapses, the ID node A 2220 a should be near the exit point and mayagain be placed into a normal operation mode so that it can seek toconnect with master node M2 2210 b.

Similar to the association process discussed with respect to ID node Aand master node M1, ID node A 2220 a and master node M2 2210 b may beassociated as ID node A 2220 a approaches master node M2 2210 b near theexit point. Once connected, the node locations and association data areupdated on the server 100. And as ID node A 2220 a continues to movethrough structure 2200, ID node A 2200 a may arrive at the exit point asshown in FIG. 22C, where the node locations and association data areupdated once again on the server 100.

Those skilled in the art will appreciate how such principles may beapplied to further movements of an ID node as it is handed off (e.g.,via active/passive associations and disassociations) between othermaster nodes and keeping track of these associations and node locationson the server 100. Additionally, as server 100 tracks and monitorsassociations, disassociations, and contextual environmental operations,server 100 essentially learns how to better use context informationbetter track nodes, manage power used by ID nodes, and enhance accuracyfor locations.

Those skilled in the art will also appreciate the general tradeoff witha level of RF power level and accuracy of location. If a node's RF powerlevel is set high, it may advertise and connect with other nodes alonger distance away. But at such a high power level setting, theability for the system to discriminate between and locate differentnodes may be a challenge.

Association Management within a Wireless Node Network

As explained above in general, management of nodes may rely uponassociations created and tracked between nodes. In some embodiments, theassociation relied upon may be an active association where the serverexpressly authorizes an active connection between nodes. In otherembodiments, the association relied upon may be a passive associationwhere the master node (a type of managing node) is associated with theother node, but not actively connected to the other node. By virtue ofthe passive association, the server may be able to keep track of andmanage the other node without requiring an active association. Thus,those skilled in the art will appreciate that in still otherembodiments, associations relied upon by the server for managing awireless node network may include both active and passive associationsand may be generally authenticated or, more specially, authorize asecure connection that has a degree of protection for the connection andcommunications using that connection.

FIGS. 23-25 provide flow diagrams of exemplary methods for associationmanagement of a wireless node network having at least a plurality ofnodes and a server in accordance with different embodiments of thepresent invention involving active and passive association examples.Those skilled in the art will appreciate that each of these exemplarymethods for association management of a wireless node network may beimplemented by instructions stored on a non-transitory computer-readablemedium, which when executed perform the steps of the respective methodsdescribed below (e.g., methods 2300, 2400, and 2500) and the describedvariations of those methods.

Referring now to FIG. 23, method 2300 begins by identifying a first nodeas a potential for actively associating with a second node at step 2305.In one example, identifying the nodes for association may involvereviewing a message sent by the first node to determine statusinformation related to the first node, and analyzing the statusinformation to determine whether the first node should be associatedwith the second node. In a further example, the status information maycomprise one of a plurality of different status levels indicatingwhether the first node is requesting a connection to the second nodewhen at that particular status level.

Next, an association request is transmitted to the server in step 2310.In one example, the association request may identify the first node andsecond node to be associated and may request transmission of one or moreappropriate security credentials (e.g., PIN credentials, securitycertificates, keys, and the like) that may be used by the nodes toenable the first and second node to securely connect and share data aspart of associating. An embodiment may request only one credential as anauthorization credential from the server. Other embodiments may use twocredentials where one may be later uses as a credential with which toreply to challenges. For example, if an ID node is challenged, the IDnode may send a reply authorization credential so that the master nodecan confirm the response and supply the ID node with the appropriatesecurity credential for the authorized association. In some cases, an IDnode may have been supplied with such a reply authorization credential(also generally referred to as a key) by the server.

At step 2315, the second node receives a permissive response from theserver related to the association request. In an example, the permissiveresponse may include receiving a first authorization credential and asecond authorization credential from the server (which may be stored onthe nodes). As such, the first authorization credential and the secondauthorization credential may be created by the server as a type ofsecurity data, and may be provided to authorize connecting the firstnode and the second node and securely sharing information between thefirst node and the second node.

With this authorization from the server, the first node and second nodemay be associated at step 2320. In one example, the method 2300 mayassociate the nodes by establishing an authorized connection from thesecond node to the first node based upon the authorization credential.And the method 2300 may securely provide shared data between the firstnode and the second node according to a profile established by theserver after the first and second nodes are associated.

In an embodiment, the method 2300 may also comprise having the secondnode gaining responsibility for a task after the second node isassociated with the first node when responsibility for the task waspreviously with the first node. For example, when the second node ispowered by an external power source and the first node is powered by abattery, this may advantageously shift the responsibility to a node thatis better suited to perform the task (e.g., has more power available orhas a power source that does not need recharging or replacing).

FIG. 24 is a flow diagram illustrating another example method forassociation management of a wireless node network in accordance with anembodiment of the invention from the perspective of the server.Referring now to FIG. 24, method 2400 begins with the server receivingan association request sent from a second of the nodes at step 2405. Theassociation request asks for permission to associate a first of thenodes to the second node.

At step 2410, the server determines a location (actual or relative) ofthe first node and second node. In one embodiment, the server mayreceive location data for the second node. For example, when the secondnode is a master node, the location data for the second node may be GPScoordinates for the current location of the master node, which providesthis to the server. And in an embodiment, the server may determine alocation of the first node using at least one of a plurality of locationmethods available to the server for locating the first node, such asthose discussed in detail above (or a combination of such methods sothat a more refined location of the first node is determined).

At step 2415, the server determines if associating the first node to thesecond node is desired based at least upon the location of the firstnode and the location of the second node. In one embodiment, it may bedetermined if associating is desired by determining if associating thefirst node to the second node is anticipated based upon context data. Inanother embodiment, it may be determined if associating is desired byidentifying a current mode of filtering that limits potential nodes tobe associated, and granting the permission to associate the first nodeto the second node only if the current mode of filtering allows thefirst node to be associated with the second node. For example, this mayinvolve granting the permission only if the current mode of filteringdefines that the second node is within a locational range of the firstnode consistent with the current mode of filtering. This may be definedby a particular filtering mode, such as a local, regional, or globalfiltering mode that operates to restrict nodes that may associate withother nodes. As such, the method may alter the current mode of filteringto another mode of filtering that allows the first node to be associatedwith the second node as a sort of override of the current filtering mode(e.g., depending upon an alert status of the first node).

At step 2420, the server records new association data if it is desiredto associate the first node with the second node at step 2420. At step2425, the server transmits a response to the second node granting thepermission to associate the first node to the second node. In anembodiment, the server may first generate an authorization credentialthat authorizes connecting the first node and the second node andsharing information between the first node and the second node. This maybe by looking up the credential information or by going through aprocess to create specific an authorization credential that allows thetwo nodes to actively pair and share data. With the authorizationcredential, the server may transmit them as the response.

In another example, the server may have pre-staged an authorizationcredential related to the second node and a third node if the serveranticipates the second node will disassociate with the first node andlater request to associate with the third node. For example, this may bedone if the context indicates the second node (e.g., a master node) maybe placed in a container and need to connect with the third node in thefuture when the second node may lose its connection to the server.

Method 2400 may also include the server receiving shared data from thesecond node. The shared data may originate from the first node or mayhave parts that originate from both the first and second nodes. Forexample, the second node may have received the permission to associate,and actively paired with the first node in a secure manner. The firstnode may have indicated it has data to upload (e.g., sensor data), andthe second node may receive the data from the first node. Subsequent tothat sharing, the second node may upload the shared sensor data from thefirst node by transmitting it to the server.

The method may further comprise instructing the second node to take overresponsibility for a task previously performed by the first node afterthe second node is associated with the first node. For example, when thesecond node is powered by an external power source and the first node ispowered by a battery, the responsibility for certain tasks may be takenover by the node with a more robust power supply (e.g., the node poweredby an external power source).

In more detail, the responsibility for certain tasks may be established,tracked and changed with a programmable profile. For example, in oneembodiment, the server may establish a profile for how long the taskresponsibility would change. In some cases, the profile may define aperiod of time for how long a node having this profile would haveresponsibility for a certain task before it would revert back to adefault node. In another example, a node (such as a master node) mayhave a default condition trigger (like a low power situation or when itcannot communicate with the server) that can override such a profile sothat it does not take on more responsibilities under particularconditions.

Furthermore, an embodiment may have the master node deciding what othernode may take on responsibility for certain tasks. This may be helpfulin situations where access to the server may be limited (e.g., anairborne environment). However, managing such a profile may be moreeasily accomplished in other embodiments with easier access to moretypes of context data on the server level.

In an embodiment that implements association management as a system,such an exemplary system for association management of a wireless nodenetwork may comprise a first node, a second node, and a server. Thesecond node includes a node processing unit, a node volatile memorycoupled to the node processing unit, a first communication interfacecoupled to the node processing unit, and a second communicationinterface coupled to the node processing unit. The first communicationinterface provides a short-range communication path between the firstnode and the second node and the second communication interface providesa longer range communication path between the second node and theserver.

The server includes a server processing unit, a server volatile memorycoupled to the processing unit, and a third communication interface thatprovides a longer range communication path between the server and thesecond communication interface of the second node.

The node volatile memory maintains at least a first program code section(e.g., master control and management code 425 or parts thereof) whilethe server volatile memory maintains at least a second program codesection (e.g., server control and management code 525 or parts thereof).

When executing the first program code section resident in the nodevolatile memory, the node processing unit of the second node isoperative to identify the first node as a potential for associating withthe second node, transmit an association request over the secondcommunication interface to the server, receive an association response(having at least authorization information generated by the server) overthe second communication interface from the server, provide theauthorization information to the first node, and associate the firstnode and the second node.

In one example, the node processing unit may be further operative toreview status information related to the first node to determine whetherthe first node desires association with the second node. In anotherexample, the node processing unit may be further operative to securelyprovide shared data between the first and second node after the firstand second node are associated and in accordance with a sharing profileprovided by the server. The sharing profile may define types ofinformation to be securely shared between particular nodes.

When executing the second program code section resident in the servervolatile memory, the server processing unit is operative to determine alocation of the first node and second node, determine if associating thefirst node to the second node is desired based at least upon thelocation of the first node and the location of the second node, storenew association data in the server volatile memory if it is desired toassociate the first node with the second node, and transmit theauthorization response to the second node granting the permission toassociate the first node to the second node.

In one embodiment, the second node in the system may take overresponsibility of a task previously handled by the first node after thesecond node is successfully associated with the first node. For example,when the second node is powered by an external power source and thefirst node is powered by a battery, the system may be more effectivelyand efficiently managed by reassigning a task (especially a task thatinvolves a significant expenditure of power, a series of operations overa significant period of time, or both) to another node, such as thesecond node, which has more power available than the first node.

In another embodiment, the server processing unit may be furtheroperative to set a current mode of filtering that limits potential nodesto be associated, and grant the permission to associate the first nodeto the second node only if the current mode of filtering allows thefirst node to be associated with the second node. In a furtherembodiment, the server processing unit may be further operative to alter(e.g., override) the current mode of filtering to a different mode offiltering. In this way, the server may adapt how nodes are managed andallow the first node to be associated with the second node if it isdesired, such as then the first node is in an alert status level andurgently is requesting connection to a larger group of nodes thanpermitted under the current mode of filtering.

While the exemplary methods illustrated in FIGS. 23 and 24 focus onactive associations, FIG. 25 is a flow diagram illustrating an examplemethod for association management of a wireless node network having atleast a plurality of nodes and a server in accordance with anembodiment, but from the perspective of a node that is to be passivelyassociated with another node. Referring now to FIG. 25, method 2500begins with a second of the nodes receiving a message broadcasted from afirst of the nodes at step 2505. At step 2510, the second node capturesan address of the first node from the message. At step 2515, the firstnode and the second node are associated by storing the captured addressof the first node and an address of the second node as association datain a memory of the second node. At step 2520, the second node transmitsthe association data to the server.

At some point, the server may be updated by the second node with updatedassociation data when the second node does not receive an additionalmessage broadcast from the first node. For example, the second node andthe first node may stay associated and securely connected for a periodof time, but eventually the first node may move such that the connectionis no longer viable or the first node may move closer to another nodealong the anticipated path it is traveling (e.g., an anticipatedshipping path along a conveyor within a structure from an entry point ofthe structure but now closer to an exit point of the structure). As thefirst node travels on the conveyor, it may get closer to another nodenear the exit point and is better managed by an association with thatother node near the exit point. Thus, the updated association datareflects that the first node is disassociated from the second node.

Method 2500 may further include having the second node determining alocation of the first node, and updating the server with a currentlocation of the second node and the determined location of the firstnode. Additionally, method 2500 may include receiving locationinformation from the server that defines a refined location of the firstnode.

In an embodiment that implements passive association management as amanaging node (e.g., a master node) in a wireless node having at leastanother node and a server, such an exemplary managing node comprises aprocessing unit, a first and second communication interface each coupledto the processing unit, a volatile memory coupled to the processingunit, and a memory storage coupled to the processing unit. The firstcommunication interface provides a first communication path to the othernode, can receive a message broadcast from the other node, and providethe message to the processing unit. The second communication interfaceproviding a second communication path to the server.

The memory storage may maintain at least a node association managermodule as program code to be executed by the processing unit. When theprocessing unit loads the module into volatile memory and executesinstructions of the module, the processing unit is operative to receivethe message from the first communication interface, capture an addressof the another node from the message, store the captured address of theanother node and an address of the managing node as part of associationdata in the memory storage, and transmit the association data to theserver through the second communication interface.

In one example, the memory storage also maintains a location managermodule and, when the processing unit also loads the location managermodule into volatile memory and executes instructions of that module,the processing unit is operative to determine a location of the othernode, determine a current location of the managing node (e.g., via GPSlocation signals), and update the server with the current location ofthe managing node and the determined location of the other node.

The managing node may be further operative to update the server withupdated association data when the first communication interface does notreceive an additional message broadcast from the other node. The updatedassociation data may reflect that the other node is disassociated fromthe managing node.

Context Management within a Wireless Node Network

As explained above in general, management of nodes may rely upon thecontextual environment of the nodes. As shown in FIG. 5, server 100 hasaccess to a wide variety of different context data 560. Context data,such as data 560, may include a wide variety of data that generallyrelates to the environment in which the nodes are operating and may beused to advantageously provide enhanced node management capabilities inaccordance with embodiments of the present invention. As such, the useof such context data provides a data foundation in an embodiment so thatthe server may better and more efficiently implement management tasksrelated to nodes in the network, and adjust such tasks to account forrelevant context data as nodes move within the network (e.g., as an IDnode moves with an item being shipped along an anticipated or predictedtransit path from an origin to a destination). For example, the servertake advantage of its ability to rely upon relevant context data toadvantageously alter how it instructs a node operate, how it associatesa node with the another node, how it can better locate a node, and howit can more efficiently track and respond to requests to report thelocation of the node.

FIG. 26 is a flow diagram illustrating an exemplary method for contextmanagement of a wireless node network in accordance with an embodimentof the invention. Referring now to FIG. 26, method 2600 begins at step2605 by identifying, by the server, at least one of the nodes. In oneexample, such as that shown in FIG. 22a , server 100 may identify IDnode A 2220 a as part of communications received from master node M12210 a. At step 2610, the server determines context data that relates toan operating environment of the identified node as the identified nodemoves within the operating environment.

In one embodiment, the context data may include one or more types ofdata, such as scan data, historic data, shipment data, RF data, andlayout data. For the example shown in FIG. 22a , server 100 may accesscontext data 560 (which may be kept in context database 565) todetermine parts of the context data 560 that relate to the operatingenvironment of ID node A 2220 a. Such context data 560 may include, inthis example, shipment data that relates the item being shipped that isconnected to ID node A 2220 a, scan data for when the item connected toID node A 2220 a was scanned upon entering structure 2200, historic datafor how long it takes a node to traverse the conveyor located withinstructure 2200, and layout data on dimensions of structure 220. Thoseskilled in the art will appreciate that context data may includeoperational environment information created within the wireless nodenetwork or created by a third party (e.g., weather information relatedto the operating environment of ID node A 2220 a).

While the server determines context data that relates to an operatingenvironment of the identified node in one embodiment, such a current oranticipated operating environment for a node in a more detailedembodiment may include one or more types of environments. For example,the current or anticipated operating environment for a node may includean electronic communication environment, a physical environment of ananticipated path along with a node moves, a conveyance environmentrelated to how a node moves, and a density environment related to thedensity of nodes within an area near a particular node identified by theserver.

Back at step 2610, the determining step may involve determining thecontext data that relates to an anticipated operating environment of theidentified node as the identified node moves in a predicted path towardsa location of another node. In another example, the determining step mayinvolve determining the context data that relates to the anticipatedoperating environment of the identified node and an anticipatedoperating environment of the another node as the identified node movesin the predicted path towards the another node for an expectedassociation with the another node

At step 2615, the server performs a management task related to theidentified node with an adjustment made to account for the determinedcontext data. When the determined context data (such as RF signaldegradation information) indicates that no adjustment is actually neededwhen performing the task, no adjustment is made given the determinedcontext data. Thus, those skilled in the art will appreciate that anadjustment may be made when needed contextually and is not required atall times.

In one embodiment, performing the management task may comprise generallyinstructing the identified node to alter its operation based upon thedetermined context data. For example, server 100 may perform themanagement task of instructing ID node A 2220 a to change itsconnectable and non-connectable intervals as it approaches master nodeM1 (which server 100 knows from context data, such as scan datagenerated when node A entered structure 2200). Thus, in this example,server 100 is able to leverage enhanced visibility of ID node A 2220 abased upon context data and advantageously alter the operation of node Ato increase the node's chance of successfully associating with masternode M1 2210 a.

In other embodiment, performing the management task may compriseassociating the identified node with another node with the adjustmentmade to alter an associating parameter based upon the determined contextdata. In other words, context data may be helpful as part of associatingnodes. In one example, the associating parameter may include at leastone altered timing interval related to associating the identified nodewith the other node, such as an alert interval or connectable interval.These intervals are parameters that may be altered as part ofadjustments made when a server associates two nodes and, for example,sets the intervals to more appropriate time durations in order toenhance the chance and opportunity the nodes have to actively pair andsecurely share data as needed.

In yet another embodiment, performing the management task may compriselocating the identified node with an adjustment made to a power settingbased upon the determined context data. In one example, the powersetting adjustment is done to a master node in direct communication withthe server. In another example, the power setting adjustment may be doneto an ID node, which is passed this operational adjustment informationfrom another node. In one embodiment, the power setting itself maycomprise an output power level adjusted to account for an adversecondition in the operating environment of the identified node (e.g., amaster node with an adjusted RF output signal level). The adversecondition may be, for example, an adverse RF communication environmentwhere structure attenuates or otherwise impedes normal RFcommunications. In another example, the adverse condition may be ahighly dense population of nodes close to the identified node.

In more detail, the output power level may be adjusted to account for ashielding condition in the operating environment of the first node. Sucha shielding condition may be caused, for example, by one or more ofpackaging, package contents, proximate package, proximate packagecontents, and physical infrastructure in the operating environment ofthe first node. For example, if the identified node is located near ametal container, it is operating in an adverse RF communicationsenvironment where it may have its output power level increased based onthis context data in order to better deal with the adverse shieldingcondition.

In still another embodiment, performing the management task may compriseproviding the location of the identified node in response to a requestreceived by the server related to a status of the identified node. Forexample, if server 100 receives a request from user access device 205about the status of ID node A 2220 a, server 100 is able to provide thelocation of node A as being within structure 2200, but refined as beingclose to the entry of the structure given the adjustment to account forcontextual data, such as scan data related to the item being shippedwith node A 2220 a.

Those skilled in the art will appreciate that method 2600 as disclosedand explained above in various embodiments may be implemented on aserver, such as server 100 illustrated in FIGS. 5 and 22A, running oneor more parts of server control and management code 525 (e.g., thecontext based node manager). Such code may be stored on a non-transitorycomputer-readable medium such as memory storage 515 on server 100. Thus,when executing code 525, the server's processing unit 500 may becomeunconventionally operative to perform operations or steps from theexemplary methods disclosed above, including method 2600 and variationsof that method.

Node Location Determination Methodologies

As part of managing and operating a wireless node network in accordancewith one or more embodiments of the invention, such as tracking ID nodeA 2220 a in FIGS. 22A-C, determining a node's location is performed. Asexplained above, an exemplary ID node may be directly or indirectlydependent on a master node to determine its location. In the embodimentsdiscussed and described herein, a location of a node may generallyencompass a current or past location. For example, an embodiment thatdetermines a node's location may be a current location if the node isnot moving, but may necessarily determine the location as a pastlocation should the node be in a state of motion.

Likewise, the term location alone may include a position with varyingdegrees of precision. For example, a location may encompass an actualposition with defined coordinates in three-dimensional space, but use ofthe term location may also include merely a relative position. Thus, theterm location is intended to have a general meaning unless otherwiseexpressly limited to a more specific type of location.

Determining node location may done by a master node alone, the serveralone, or the master node working together with the server. And on suchdevices, embodiments may use one or more methodologies to determine anode's location and further refine the location. Such examplemethodologies may include, but are not limited to, determining nodelocation may relate to controlling an RF characteristic of a node (e.g.,an RF output signal level and/or RF receiver sensitivity level),determining relative proximity, considering association information,considering location adjustments for context information and an RFenvironment, chaining triangulation, as well as hierarchical andadaptive methods that combine various location methodologies. A moredetailed description of these exemplary node location determinationtechniques is provided below.

Location Through Proximity

In one embodiment, a signal strength measurement between two or morenodes may be used to determine the proximity of the nodes. If neithernode's actual location is known, one embodiment may infer a locationrelationship of the two nodes through proximity.

Proximity when Varying Power Characteristics

For example, an exemplary method of determining a node's location in awireless node network of nodes may involve varying a node's powercharacteristic, such as the output power of one of the nodes. Generallyand as explained with reference to FIG. 13, the power characteristic maybe varied to identify closer ones of the nodes to the node broadcasting.The node broadcasting may transmit one or a series of signals whileother nodes may report receiving one or more of the signals. Those othernodes that receive at least one signal broadcast from the transmittingnode may be deemed part of a close group of nodes. And as the powercharacteristic is varied (increased or decreased or both), a closestgroup of nodes (or single node) may be identified as the smallest groupof nodes of those that receive at least one signal from the broadcastingnode. Accordingly, while not absolute, a type of location for thebroadcasting node may be determined based on the closest one or group ofnodes. This may be repeated for neighboring nodes to yield a set ofclosest node information for each of the nodes. In more detail, anexemplary set of closest node information for each of the nodes mayinclude which nodes are closest (via the lowest power characteristic)and more robustly supplement this information with which other nodes areincrementally further away (via increasingly larger powercharacteristics). Thus, the set of closest node information provides thebasis for a determination of how close the nodes in the network are toeach other, which provides a type of location determination for eachnode.

Additionally, context data may be referenced in certain embodiments tofurther enhance determining how close the nodes are to each other. Forexample, combining the set of closest node information with contextdata, such as scan information that registers when an item changescustodial control in a delivery system, may further refine how todetermine the location of the nodes. Scan and other context informationwill help determine if one or more of the nodes, for example, are knownto be in the same container, vehicle or moving on a belt together. Thus,this type of context data may be integrated into a further step ofrefining how close the nodes are to each other based upon the contextdata.

In general, a location of a node based upon proximity may be determinedwhen a power characteristic of nodes is changed or varied in a wirelessnode network. FIG. 28 is a flow diagram illustrating an exemplary methodfor location determination by varying a power characteristic of nodes ina wireless node network in accordance with an embodiment of theinvention. Referring now to FIG. 28, method 2800 begins by at step 2805by instructing a first of the nodes to vary the power characteristic forone or more signals broadcast by the first node. In a more detailedembodiment, such an instruction may cause the first node, for example,to incrementally decrease or incrementally increase the powercharacteristic (such as an output power level) between values.

At step 2810, method 2800 continues by identifying a first group ofother nodes in the wireless node network that are near the first nodebased upon those of the other nodes that received at least one of thesignals broadcast by the first node as the first node varies the powercharacteristic. In a further embodiment, step 2810 may incrementallyidentifying which of the first group of other nodes are receiving atleast one of the broadcast signals as the first node incrementallyvaries the output power level of the signals broadcast. Theincrementally identified nodes may be deemed a set of increasingly closenodes to the first node.

At step 2815, method 2800 continues by identifying a closest one or moreof the other nodes as a smallest group of the other nodes that receivedat least one of the one or more signals broadcast by the first node asthe first node varies the power characteristic.

At step 2820, method 2800 concludes by determining a location of thefirst node based upon the closest one or more of the other nodes. Thus,as the power characteristic is varied, the group of nodes that havereceived at least one of the signals broadcast by the first node maychange and the smallest such group being a closest group of nodes (evenif just one node) to the first node. In a more detailed embodiment, step2820 may comprise determining the location of the first node based uponthe closest one or more of the other nodes and the set of increasinglyclose nodes to the first node as the set of increasingly close nodesprovides more detailed proximity information for a refined locationdetermination.

For example, referring to FIG. 14, the set of increasingly close nodesto the ID node F 920 f may include node M3 as being farthest away and M1being closer than M3. When the power characteristic of ID node Fincrementally decreases, and its output power level changes from P1 toP2, M3 can no longer receive the signal, but M1 and M2 still do. And asthe power characteristic of ID node F continues to incrementallydecrease, and its output power level is changed from P2 to P3, M1 can nolonger receive the signal, but only M2 does as the last of the nodesclosest to ID node F. Thus, in this example, determining the location ofID node F may be based upon the fact that M2 is the closest node and theset of increasingly close nodes include M1 and M3 with M1 being closerthan M3.

In another embodiment, one or more further refinements to the firstnodes location may be performed. In one example, steps 2805-2820 may berepeated where a second of the nodes is instructed to vary the powercharacteristic for one or more signals broadcast by the second node, andthen method 2800 may further refine the location of the first node basedupon a location of the second node. In a more detailed example, steps2805-2820 may be repeated where a second of the nodes is instructed tovary the power characteristic for one or more signals broadcast by thesecond node, and then method 2800 may further the location of the firstnode based upon a location of the second node and a set of increasinglyclose nodes to the second node. With this increasingly cross-relatedinformation on what nodes are closer to other nodes and to what degree,which may be further repeated for additional nodes, embodiments mayfurther refine the location of the first node within the network.

Method 2800 may further include determining context data related to thefirst node, and refining the location of the first node based upon thecontext data. In an embodiment where the power characteristic is outputpower level, the incremental changes in the output power level of thebroadcast signal in steps 2805-2815 may be set according to the contextdata.

Method 2800 may also determine the context data to be related to theclosest node to the first node, and refine the location of the firstnode based upon the context data. In still another example, method 2800may determine the context data to be related to the incrementallyidentified nodes in the set of increasingly close nodes to the firstnode, and refining the location of the first node based upon the contextdata. For example, the closest node and the set of increasingly closenodes may have scan data that indicate they are within the samecontainer. This exemplary context data may be used to further refine thelocation of the node being located, which may help efficiently determinethat node is near the container. As such, those skilled in the willappreciate that context data for the node being located as well as nodesidentified to be close to that node may provide relevant input toadvantageously help further refine the location of the node.

Those skilled in the art will appreciate that method 2800 as disclosedand explained above in various embodiments may be implemented on aserver apparatus, such as server 100 illustrated in FIGS. 5 and 22A,running one or more parts of server control and management code 525(e.g., the location manager). Such code may be stored on anon-transitory computer-readable medium such as memory storage 515 onserver 100. Thus, when executing code 525, the server's processing unit500 may be programmatically transformed to become unconventionallyoperative to perform operations or steps from the exemplary methodsdisclosed above, including method 2800 and variations of that method.

An embodiment of such a server apparatus may include a server (such asserver 100) operative to communicate with a plurality of nodes in thewireless node network. As explained with respect to FIG. 5, the servergenerally includes a server processing unit, a server volatile memory, aserver memory storage, and at least one communication interface. In thisembodiment, the volatile memory, memory storage, and communicationinterface are each coupled to the processing unit. The memory storagemaintains at least a program code section and location data related to alocation of one or more of the nodes. The communication interfaceprovides a communication path operatively coupling the server with thenodes.

The server processing unit, as mentioned above, is operative whenrunning the program code section, to perform the steps and operations asdescribed above relative to method 2800 and variations of that methoddescribed above.

Proximity when Observing Signal Patterns and Strengths Over a TimePeriod

In another embodiment, an improved method for determining a node'slocation through proximity may include analyzing the signal patterns andstrengths between an advertising node and a listening node. In oneembodiment, a threshold may be set for association based on an observedmessage count and/or recorded signal strength within a specific timeperiod may improve the ability to locate a node (e.g., an ID node) tothat of another node (e.g., a master node). In some embodiments, theobserved message count may be implemented as an averaged count over arepeated time periods. Further still, other embodiments may filteroutlying observations in the observation data set to help improve thequality of data relied upon for setting a threshold for association and,as a result, determine a node's location.

In a more detailed example, an improved method for determining a node'slocation through proximity may show captured advertising message countsas a component for a node's location and determining a node's directionof travel. In this example, two exemplary master nodes (e.g., masternode M1 910 a and M2 910 b) may capture advertising messages from one IDnode (e.g., ID node A 920 a). Master node M1 may observe and capture(e.g., record information related to the observation) 60 messages fromID node A within a 2 minute period, while master node M2 only observesand captures 7 advertising messages from ID node A within that sameperiod. Based upon the difference in how often messages are observedfrom ID node A by master node M1 compared to those observed by masternode M2, the system is able to determine that ID node A would moreproximate to master node M1, and it's known location.

In a further embodiment, comparing the average time stamp of thecaptured records may allow the system can make a more accuratedetermination of location. For example, if the average captured messagefound on master node M2 is increasingly growing larger (e.g., takinglonger for messages to go from ID node A to master node M2), thisindicates ID node A is moving away from master node M2. If the averagecaptured message found on master node M2 is growing increasingly largerwhile the average captured message found on master node M1 isincreasingly growing smaller, this indicates ID node A is moving awayfrom master node M2 and toward master node M1. Thus, over a number ofobserved time periods, the change in message timing (transmission toreception) may also be relied upon to enhance or refine a node'slocation.

In yet another embodiment, the observed signal strength may be acomponent in location determination and estimating direction of traveland may allow the system can make a more accurate determination oflocation. For example, two master nodes (M1 910 a and M2 920 b) may becapturing advertising messages from a node (ID node A 920 a). M1captures 60 messages from ID node A within 2 minutes, while M2 capturesonly 7 messages. The average signal strength observed for signals fromID node A by master node M1 is higher compared to the average signalstrength observed by master node M2. Based upon this observed signalstrength information, the system would determine that ID node A to be atM1, but a predicted path may indicate ID node A is heading towards M2.As the master nodes M1 and M2 continue to capture records, the system(e.g., management code 524 operating on server 900, which is incommunication with M1 and M2) processes the continued feed of capturerecords from M1 and M2. With this observed signal strength information,the server 900 would expect that the count and average signal strengthof messages from ID node A over the time period observed (2 minutes) toincrease for observations at M2 and to decrease for observations at M1when ID node A is physically moving closer to M2 and away from M1. Thus,the change in observed powers levels and in how often messages areobserved may indicate actual node movement in an embodiment.

Basing node proximity location and node directional determinations onobserved signal patterns and characteristic strengths over a period oftime has the advantage of reducing the likelihood of unwanted andspurious signal anomalies causing an ID node's location to beincorrectly determined. And the above exemplary methods for determiningmovement characteristics of a node (e.g., moving closer to one node,moving closer to one but away from another, etc.) as part of refiningthe node location may be applied in combination with the variousembodiments for determining node location described herein.

FIG. 27 is a flow diagram illustrating an exemplary method for proximitylocating a node in a wireless node network based upon observed signalpatterns and characteristic indications over a period of time inaccordance with an embodiment of the invention. Referring now to FIG.27, method 2700 begins at step 2705 by instructing a first and a secondother nodes to detect any message broadcast from the one node over aperiod of time. The period of time may be set based upon a variety offactors, such as context data. In more detail, the period of time may bedynamically changed based upon context data as the one node moves intodifferent contextual environments.

Method 2700 has the server receiving a first indication from the firstother node at step 2710 and receiving a second indication from thesecond other node at step 2715. Finally, the method 2700 determines alocation of the one node based upon a difference in the first indicationand the second indication at step 2720.

The first indication is related to a characteristic of messagesbroadcast from the one node that are detected by the first other nodeduring the period of time. Likewise, the second indication is related tothe characteristic of messages broadcast from the one node that aredetected by the second other node during the period of time. Theseindications may include, for example, a count of messages received bythe respective other nodes, a transit time factor (e.g., an averagetransit time for a message to be detected after broadcast), and anaverage signal strength.

In one embodiment, the first indication may be a first count of messagesbroadcast from the one node that are detected by the first other nodeduring the period of time, and the second indication may be a secondcount of messages broadcast from the one node that are detected by thesecond other node during the period of time. As such, determining thelocation of the one node may be the location that is closer to the firstother node than the second other node when the first count is greaterthan the second count. Additionally, the method 2700 may further includedetermining an actual node movement direction for the one node basedupon comparing the first count and the second count over a plurality oftime periods. For example, the method 2700 may repeat observations overseveral of these time periods and track the first count and second countover time to determine which is increasing, which is decreasing, anddetermine movement of the one node based upon these measurements overtime.

In another detailed embodiment, the first indication may be a first timefactor of messages broadcast from the one node that are detected by thefirst other node during the predetermined time period, and the secondindication may be a second time factor of messages broadcast from theone node that are detected by the second other node during the period oftime. And an actual node movement direction for the one node may bebased upon comparing the first time factor and the second time factor.In a more detailed embodiment, the first time factor may be an averagetransit time for a message detected at the first other node to go fromthe one node to the first other node, and the second time factor is anaverage transit time for a message detected at the second other node togo from the one node to the second other node. As such, determining thelocation of the one node may be that the location is closer to the firstother node than the second other node when the first time factor is lessthan the second time factor.

In yet another embodiment, the first indication may be a first averagesignal strength of messages broadcast from the one node that aredetected by the first other node during the period of time, and thesecond indication may be a second average signal strength of messagesbroadcast from the one node that are detected by the second other nodeduring the period of time. As such, determining the location of the onenode may be that the location is closer to the first other node than thesecond other node when the first average signal strength is greater thanthe second average signal strength.

The method 2700 may also include, in an embodiment, observing a degreeof change in the first average signal strength and a degree of change inthe second average signal strength over repeated time periods, anddetermining an actual node movement direction for the one node basedupon comparing the degree of change in the first average signal strengthand the degree of change in the second average signal strength.

In another embodiment, the method 2700 may also refine the determinedlocation of the one node. In this embodiment, the method 2700 mayfurther comprise refining the location of the one node based upon atleast one of a first updated location received from the first other nodeand a second updated location received from the second other node. Forexample, when first other node is a mobile master node and it is thecloser of the two nodes to the one node being located, the embodimentcan take advantage of the location signaling onboard the first othernode that provides the current location of the first other node. Thatcurrent location data may be transmitted by the first other node to theserver to update the server in its calculation of the location for theone node.

In still another embodiment, the method 2700 may layer context data withthe determined location to refine the location of the node. Context datarelated to the one node may be determined by the server, and so thelocation of the one node may be refined based upon that context data. Inanother example, context data related to the closer of the first othernode and the second other node when compared to the location of the onenode. For example, the server may be aware that a particular master nodeis closer to the one node compared to a second master node, and that theparticular master node is within a container. With this additionalcontext data related to the particular master node, the server mayrefine the location of the one node based upon the context data. Otherexemplary types of relevant context data may be relied upon whenrefining the location of the one node, such as context data of aparticular shielding associated with the environment near the particularmaster node (e.g., a particular type of ULD having known RF shieldingcharacteristics, etc.)

Additionally, the method 2700 may involve looking to see if the one nodeis behaving as expected. More specifically, a further embodiment of themethod 2700 may further compare the location of the one node to apredicted path of the one node to determine if the one node is locatedoutside the predicted path. This may allow the server to use learned,historic data when creating a predicted path, and keep track of the onenode relative to being within an acceptable range associated with thispredicted path. The method may also generate a notification if the onenode is outside the predicted path. In this manner, actionable tasks canthen be taken to locate the one node—e.g., changing filter mode optionsfor nodes in that general area, etc.

Those skilled in the art will appreciate that method 2700 as disclosedand explained above in various embodiments may be implemented on aserver, such as server 100 illustrated in FIGS. 5 and 22A, running oneor more parts of server control and management code 525 (e.g., thelocation manager). Such code may be stored on a non-transitorycomputer-readable medium such as memory storage 515 on server 100. Thus,when executing code 525, the server's processing unit 500 may beprogrammatically transformed to become unconventionally operative toperform operations or steps from the exemplary methods disclosed above,including method 2700 and variations of that method.

Association Driven Locating with Variable RF Characteristics

As noted above, a signal strength measurement between two or more nodesmay be used to determine relative distance between nodes. If one of thenodes has a known location (such as master node M1 910 a), a relativelocation of one or more nodes within a range of the known location nodeis generally a function of how accurate the system may determine adistance between the node with known location and associated nodes. Inother words, an embodiment may identify a relative location of an itemand its related node by relying upon association-driven variablelow-power RF output signals to determine a distance the node is from aknown location.

Location Determination Through Master Node Advertise

As generally mentioned above, determining node location may relate tocontrolling an RF characteristic of a node (e.g., an RF output signallevel and/or RF receiver sensitivity level) and, more specifically, mayinvolve aspects of controlling master node advertising. FIG. 13 is adiagram illustrating an exemplary location determination using masternode advertise in accordance with an embodiment of the invention. In theillustrated embodiment shown in FIG. 13, a master node, such as masternode M1 910 a, with a known location is broadcasting an advertisingmessage at varying RF output power levels. FIG. 13 illustrates theexemplary different RF output power levels as concentric ranges1305-1315 about master node M1 910 a. Thus, master node M1 910 a maybroadcast at a maximum power P1, related to range 1305, but may controlthe RF output power level and dynamically change the RF output powerlevel to P2 and broadcast at a smaller range 1310, or to P3 andbroadcast to an even smaller range 1315.

In the illustrated embodiment, receiving ID nodes A-E 920 a-920 e are inquery (scan) mode and can each use the received signal at differentlevels to determine how far away from the transmitting M1 they arelocated. Those skilled in the art will appreciate that while theillustrated embodiment shown in FIG. 13 has the receiving nodes all asID nodes, other embodiments may have receiving nodes be either master orID nodes or a mixture.

In the exemplary embodiment of FIG. 13, the location for nodes A-E maybe determined based upon the known location of master node M1 910 a.That location, plus a range measurement when each of respectivereceiving nodes A-E last receives a signal from node M1, and factoringin a confidence factor of the range measurement, provides a locationdetermination for the nodes according to variable RF signal power.Depending on a quality of the range measurement, the individualreceiving nodes may or may not have an individually calculated location.In yet another embodiment, if third party or context data, such as scaninformation, is available, a refined location may be determined usingsuch data as an additional confidence factor. As the communication rangeof M1 is limited from P1 to P3, the accuracy of location by associationgoes up.

In the illustrated example of FIG. 13, an exemplary method ofdetermining a node's location may be described that uses master nodeadvertising. First, when the master node M1's variable power short rangecommunication interface 480 is set to P1, its maximum output, masternode M1 910 a is seen by each of ID nodes A-E 920 a-920 e. Based uponanalytics or historic measurements, the open air performance (optimalrange) of the radio in M1's variable power short range communicationinterface 480 at P1 power level may have been previously been found tobe approximately 30 feet. Thus, without the need to examine RSSI levelsfrom the individual ID nodes A-E 920 a-920 e and without the need foractive calibration phases, the system may know that ID nodes A-E arewithin 30 feet of master node M1 910 a.

Next, when the master node M1's variable power short range communicationinterface 480 is set to P2, a medium output level in this example,master node M1 is seen by nodes A and B. From previous analytics orhistoric measurements, it was determined the open air performance(optimal range) of the master node M1's variable power short rangecommunication interface 480 running at P2 power level is approximately15 feet. Thus, without the need to examine RSSI levels from theindividual nodes, we know ID nodes A 920 a and B 920 b are within 15feet of master node M1. Furthermore, we know the ID nodes no longerreceiving the broadcasted RF signal from master node M1 910 a (e.g., IDnodes C 920 c, D 920 d, and E 920 e) are somewhere within 30 feet ofmaster node M1 910 a, but probably more than 15 feet away from M1.

And when the master node M1's variable power short range communicationinterface 480 is set to P3, its minimum output level in this example, itis seen by ID node B 920 b. From previous analytics or historicmeasurements, it was determined the open air performance (optimal range)of the master node M1's variable power short range communicationinterface 480 running at P3 power level is approximately 5 feet. Thus,without the need to examine RSSI levels from the individual ID nodes, weknow the location of ID node B 920 b is within 5 feet of the knownlocation of master node M1 910 a.

The ranging steps, as discussed in the example above, may then berepeated for any of the identified nodes in order to build a moreaccurate picture of the relative location of each node. The granularityof RF characteristic settings (e.g., the RF output signal power levelsetting) will provide more granularity of location differentiation whenperforming the ranging steps. In one embodiment, the ranging steps maybe performed over a set of gross RF characteristics settings (e.g., fewsettings over a wide range), and similar steps may then be performedover more select ranges for the RF characteristics settings.

FIG. 29 is a flow diagram illustrating an exemplary method for locationdetermination using one or more associations of nodes in a wireless nodenetwork in accordance with an embodiment of the invention. Referring nowto FIG. 29, method 2900 begins at step 2905 where a first of the nodesbroadcasts one or more first messages at a first anticipated orpredicted range distance. In one embodiment, the first anticipated rangedistance is an optimal range for the first node. For example, the firstnode's radio in its communication interface may have a maximum settingto allow the node to broadcast at maximized range assuming a clearenvironment. Such a setting provides a known anticipated range distance.In the example of FIG. 13, master node M1 910 a may be broadcasting at amaximum power level P1 that reaches a first range distance from node M1.However, if node M1 is known to be within an adverse RF shieldingenvironment, the first anticipated range distance may be a distanceadjusted to account for the contextual environment of such shielding(e.g., a type of context data). Anticipated range distances may beadjusted depending upon one or more types of relevant context (e.g., oneor more types of context data related to how an RF output signal fromthe node may be impeded).

At step 2910, method 2900 identifies which of the nodes associated withthe first node received at least one of the first messages. In oneembodiment, the first node may be able to access and review associationdata in its onboard memory storage as part of identifying which are thenodes associated with it. In one example, the associations with thefirst node may be passive associations (e.g., not actively paired andsecurely connected) or active associations (e.g., actively paired andable to securely connect and share data), or a combination of both typesof associations.

Next, at step 2915, the first node broadcasts one or more secondmessages at a second anticipated range distance, which is incrementallysmaller than the first anticipated range distance. In the example ofFIG. 13, master node M1 910 a may be the first node and now isbroadcasting at a medium power level P2 that reaches a secondanticipated range distance from node M1. By incrementally changing theRF power level in this manner, master node M1 910 a now no longer canreach nodes C-E as shown in FIG. 13.

At step 2920, method 2900 concludes by determining a location of one ormore of the identified associated nodes that did not receive any of thesecond messages but received at least one of the first messages, wherethe location is between the first and second anticipated range distancesfrom the first node. Again, in the example of FIG. 13, master node M1910 a may determine the location of nodes C-E (given they did notreceive the message sent out the second anticipated range distance at RFpower level P2) to between the first anticipated range distance (whenmaster node M1 was broadcasting at power level P1) and the secondanticipated range distance (when master node M1 was broadcasting atpower level P2) from the known location of master node M1.

In one embodiment, the method 2900 may also have the first nodebroadcasting one or more third messages at a third anticipated rangedistance (incrementally smaller range than the second anticipated rangedistance), and determining a location of one or more of the identifiedassociated nodes that did not receive any of the third messages butreceived at least one of the second messages, where the location isapproximately near the second anticipated range distance from the firstnode. Again, in the example of FIG. 13, by incrementally changing thepower level down to P1 and broadcasting a third message at ananticipated range distance for that P1 level, the master node M1 candetermine the location of node A (as node A received the second messagebut did not receive the third message) to be approximately near theanticipated range distance for P2 from the location of master node M1.

Additional embodiments of method 2900 may also refine such determinedlocations by updating the location of the first node. In one embodiment,the first node may be a mobile node. As such, refining may involvedetermining a current mobile location of the first node, and refiningthe location of the one or more of the identified associated nodes thatdid not receive any of the second messages but received at least one ofthe first messages based upon the current mobile location of the firstnode. Thus, as the first node moves and updates its own location (e.g.,via GPS signals received by location circuitry 475 on a master node),the first node is able to leverage its own updated location andadvantageously refine the location of nodes associated with it.

And, in some embodiments, the refined location of associated nodes maybe transmitted to a server. This provides an update to the server, andaids in tracking and managing the location of nodes in the network.Again, referring back to the example of FIG. 13, master node M1 910 amay take advantage of such a method for locating associated nodes, suchas the locations of ID nodes A-E 920 a-920 e, and update server 100 withthis new location data related to the current location of node M1 andany of the nodes associated with node M1.

Those skilled in the art will appreciate that method 2900 as disclosedand explained above in various embodiments may be implemented on a node(e.g., master node 110 a in FIG. 4, master node M1 910 a in FIG. 13, ormaster node M1 2210 a in FIG. 22A) running one or more parts of mastercontrol and management code 425 (e.g., the location aware/capturemodule). Such code may be stored on a non-transitory computer-readablemedium, such as memory storage 415 on master node 110 a. Thus, whenexecuting code 425, the master node's processing unit 400 may beprogrammatically transformed to become unconventionally operative toperform operations or steps from the exemplary methods disclosed above,including method 2900 and variations of that method.

In another embodiment, a node apparatus is described in a wireless nodenetwork that uses location determination by association as describedwith reference to the steps related to method 2900. As mentioned above,such as node apparatus may be implemented with a master node having anode processing unit, a node volatile memory, a node memory storage, anda first and second communication interface. Each of the memories andcommunication interfaces are coupled to the node processing unit.Further, the node memory storage maintains at least a program codesection, association data, and location data and, at times, shippinginformation. The first communication interface provides a firstcommunication path operatively coupling the node with a plurality ofother nodes in the network, while the second communication interfaceprovides a second communication path operatively and separately couplingthe node with a server in the network.

In this embodiment, the node processing unit is operative to transmitone or more first messages via the first communication interface at afirst anticipated range distance, and identify which of the others nodesthat are associated with the first node received at least one of thefirst messages. In one embodiment, the node processing unit may beoperative to access the association data in the node memory storage whenidentifying which of the nodes associated (e.g., passive, active, orboth types of associations) with the first node received at least one ofthe first messages.

The first anticipated range distance may be an optimal transmissionrange for the first communication interface and, in a more detailedexample, may be adjusted based upon context data (e.g., RF shieldinginherent from the surrounding environment of the node). In yet anotherembodiment, the first anticipated range distance and the secondanticipated range distance may be adjusted based upon one or more typesof context data related to how an RF output signal transmit from thefirst communication interface may be impeded by an environment of thenode.

The node processing unit is also operative to transmit one or moresecond messages via the first communication interface at a secondanticipate range distance (incrementally smaller than the firstanticipated range distance) and determine a location of one or more ofthe identified associated nodes that did not receive any of the secondmessages but received at least one of the first messages. That locationis between the first anticipate range distance from a known location ofthe node and the second anticipated range distance from the knownlocation of the node. In a further example, the node processing unit maybe operative to store the determined location in the node memory storageas part of the location data.

The node processing unit may also be operative to transmit one or morethird messages via the first communication interface at a thirdanticipated range distance (incrementally smaller range than the secondanticipated range distance) and determine a location of one or more ofthe identified associated nodes that did not receive any of the thirdmessages but received at least one of the second messages, where thelocation is between the second anticipated range distance from the knownlocation of the node and the third anticipated range distance from theknown location of the node.

In another embodiment, the node may be mobile and the node processingunit may be further operative to refine the location of the one or moreof the identified associated nodes that did not receive the secondmessage but received the first message by updating a location of thefirst node. In more detail, the node processing unit may be operative todetermine a current mobile location of the first node (e.g., check withlocation circuitry onboard the node for valid GPS signals and a locationlock based on such signals), and refine the location of the one or moreof the identified associated nodes that did not receive any of thesecond messages but received at least one of the first messages basedupon the current mobile location of the first node. The node processingunit may also be operative to transmit the refined location to theserver over the second communication interface.

Location Determination Through ID Node Advertise

While FIG. 13 provides an example of location determination throughmaster node advertising, FIG. 14 focuses on location determinationthrough ID node advertising. In particular, FIG. 14 is a diagramillustrating an exemplary location determination using ID node advertisein accordance with an embodiment of the invention. In the illustratedembodiment shown in FIG. 14, exemplary ID node F 920 f is in anadvertising mode but is without a known location. As with FIG. 13, FIG.14 illustrates the exemplary different RF output power levels from IDnode F 920 f as concentric ranges 1405-1415 about ID node F 920 f. Thus,ID node F 920 f may broadcast at a maximum power P1, related to range1405, but may control the RF output power level and dynamically changethe RF output power level to P2 and broadcast at a smaller range 1410,or to P3 and broadcast to an even smaller range 1415. Master nodes M1-M3910 a-910 c are disposed in various known locations relatively near IDnode F 920 f, which has an unknown location. As such, ID node F 920 fmay take advantage of the ability to adjust an RF characteristic, suchas RF output signal power level, of its own short-range communicationinterface as part of how the system may determine location of ID node Fthrough ID node advertising.

In the illustrated embodiment, an RF output signal power level of IDnode F 920 f may be varied or dynamically adjusted via programmablesettings (such as profile settings or parameters) related to operationsof variable power short range communication interface 375. Additionally,while an actual communication range may vary with the surroundingenvironment, a maximum anticipated communication range of the ID node'stransmitter at each power level is known assuming an optimal operatingenvironment or no substantial RF shielding or interference. Thus, aparticular power level setting for a broadcasting node is inherentlyassociated with a corresponding anticipated range distance.

In an exemplary method of determining a nodes location using ID nodeadvertising, the RF output signal power level may be varied acrossmultiple power levels to improve location through master nodeassociation. In more detail, when the ID node F's variable power shortrange communication interface 375 is set to P1, its maximum output, IDnode F 920 f is seen by each of master nodes M1-3 910 a-910 c. Theanticipated open air performance or range distance (optimal range, orrange based upon analytics or historic measurements) of the radio in IDnode F's variable power short range communication interface 375 at P1power level may have been previously been found to be approximately 30feet. Thus, without any examination of RSSI levels from the individualmaster nodes, the system knows ID Node F is within 30 feet of masternodes M1-M3.

Next, when the ID node F's variable power short range communicationinterface 375 is set to P2, a medium output level in this example, IDnode F 920 f is seen by master nodes M1 910 a and M2 910 b. Theanticipated open air performance or range distance (optimal range, orrange based upon analytics or historic measurements) of the radio in IDnode F's variable power short range communication interface 375 atrunning at P2 power level is approximately 15 feet. Thus, without anyexamination of RSSI levels from the individual nodes, we know masternodes M1 910 a and M2 910 b are within 15 feet of ID node F 920 f inthis example. Furthermore, we know the master node no longer receivingthe broadcasted RF signal from ID node F 920 f (e.g., master node M3 910c) is somewhere within 30 feet of ID node F 920 f, but probably morethan 15 feet away from node F in this example.

And when ID node F's variable power short range communication interface375 is set to P3, its minimum output level in this example, ID node F920 f is seen by only master node M2 910 b. The anticipated open airperformance or range distance (optimal range, or range based uponanalytics or historic measurements) of the radio in ID node F's variablepower short range communication interface 375 at P3 power level isapproximately 5 feet. Thus, without any examination of RSSI levels fromthe master nodes, we know the location of ID node F 920 f is within 5feet of the known location of master node M2 910 b in this example.

The ranging steps with respect to the changed RF characteristics of anadvertising ID node, as discussed in the example above, may then berepeated for any of the identified nodes in order to building a morecomplete picture of the relative location of each node.

Furthermore, the timing between such ranging steps may vary dynamicallydepending upon whether the node is moving. Those skilled in the art willappreciate that when moving, a quicker flow through such ranging stepswill help to provide better accuracy given the movement of nodes. Thus,the time interval between instructing a node to broadcast one or moremessages at a particular power level and then instructing that node tobroadcast one or more messages at a different power level may be desiredto be shorter when the node is moving, which can be determined basedupon context data. For example, the context data may indicate the nodeis within a node package an on a moving conveyor system. As such, thenode is moving relative to fixed master nodes that may be positionedalong the conveyor system. Thus, server may have the first node performthe ranging steps where power is varied in relative quick successioncompared to a situation where the context data indicates the node is notmoving or is substantially stationary.

FIG. 30 is a flow diagram illustrating another exemplary method forlocation determination using one or more associations of nodes in awireless node network in accordance with an embodiment of the invention.Referring to FIG. 30 and how it explains a particular way to locate anode using associations and master node one or more master nodeadvertising techniques, method 3000 begins at step 3005 by instructing afirst of the nodes to broadcast one or more first messages at a firstpower level, the first power level being related to a first anticipatedrange distance. In one example, the first anticipated range distance maybe an optimal range for the first of the nodes (e.g., a transmissionrange that assumes there are no obstructions and a clear signal pathbetween nodes). In another example, the first anticipated range distancemay be an optimal range for the first node adjusted based upon contextdata (e.g., data related to the surrounding RF environment of the firstnode).

At step 3010, the method 3000 identifies which of the nodes associatedwith the first node have known locations at step 3010. For example, thistype of identification may be accomplished by reviewing association datathat indicates which of the nodes are associated with the first node(e.g., via passive association, via active association, or via acombination of both), determining which of the nodes are associated withthe first node based upon the reviewed association data, and identifyingwhich of those associated nodes have known locations.

The method 3000 continues at step 3015 by determining which of theidentified associated nodes received at least one of the first messages.Next, the method 3000 instructs the first node at step 3020 to broadcastone or more second messages at a second power level, where the secondpower level is related to a second anticipated range distance and thesecond power level incrementally smaller than the first power level. Ina further example, the first anticipated range distance and the secondanticipated range distance may be adjusted based upon one or more typesof context data related to how an RF output signal from the first nodemay be impeded.

At step 3025, method 3000 determines which of the identified associatednodes received at least one of the second messages. Method 3000concludes at step 3030 where the method determines a location of thefirst node to be at or between the first anticipated range distance andthe second anticipated range distance from each of the identifiedassociated nodes that did not receive at least one of the secondmessages but received at least one of the first messages.

As mentioned above, determining the node's location may be improved whenaccounting for movement. As such, an embodiment of method 3000 mayinstruct the first node to broadcast the one or more second messageswithin a time interval after instructing the first node to broadcast theone or more first messages. The time interval may be predetermined insome implementations, but also may be a dynamically set parameter inother implementations based upon context data related to the first node.In more detail, the time interval may be reduced from a prior value whenthe context data related to the first node indicates the first node ismoving, but may be increased from a prior value when the context datarelated to the first node indicates the first node is substantiallystationary.

In another embodiment, method 3000 may further include instructing thefirst node to broadcast one or more third messages at a third powerlevel. Such a third power level is related to a third anticipated rangedistance and incrementally smaller range than the second anticipatedrange distance. Thereafter, the method may determining the location ofthe first node to be at or between the second anticipated range distanceand the third anticipated range distance from each of the identifiedassociated nodes that did not receive any of the third messages butreceived at least one of the second messages.

In another embodiment, method 3000 may comprise refining the location ofthe first node with an updated location of one or more of the identifiedassociated nodes that did not receive at least one of the secondmessages but received at least one of the first messages. For example,if the first node is associated with a mobile master node, the locationof the first node may be refined with an updated location of the mobilemaster node (which may be closer to the first node than previouslydetermined).

In a further embodiment, the first node in the operation of method 3000may not be self-aware of its own location. In another embodiment, thefirst node in the operation of method 3000 may have been previouslyself-aware of the location of the first node but may no longer beself-aware of the location of the first node prior to broadcasting theone or more first messages. In more detail, the first node may no longerbe self-aware of the location of the first node prior to broadcastingthe first message because of a change in the environment surrounding thefirst node. Such a change in the environment may be, for example, whenthe first node has moved inside a structure (e.g., building, vehicle,aircraft, container, etc.) that blocks location signals from beingreceived by the first node.

Those skilled in the art will appreciate that method 3000 as disclosedand explained above in various embodiments may be implemented on a node(e.g., master node 110 a in FIG. 4) running one or more parts of mastercontrol and management code 425 (e.g., the location aware/capturemodule) to control operations of an ID node (such as ID node F in FIG.14) as part of location determination via ID node advertising. Such codemay be stored on a non-transitory computer-readable medium, such asmemory storage 415 on master node 110 a. Thus, when executing code 425,the master node's processing unit 400 may be programmaticallytransformed to become unconventionally operative to perform operationsor steps from the exemplary methods disclosed above, including method3000 and variations of that method.

From an apparatus perspective, an exemplary node apparatus in a wirelessnode network that uses location determination by association maycomprises a node processing unit, node memory coupled to and used by thenode processing unit (e.g., a node volatile memory and a node memorystorage). The node memory storage maintains at least a program codesection, association data, and location data. The node apparatus furtherincludes a first communication interface that provides a firstcommunication path coupled to the node processing unit and operativelycoupling the node with a plurality of other nodes in the network. Forexample, the master node 110 illustrated in FIG. 4 includes such typesof operational structure.

The node processing unit (e.g., processing unit 400 of master node 110a), when executing at least the program code section resident in thenode volatile memory, is operative to perform specific functions orsteps. In particular, the node processing unit is operative tocommunicate an instruction to a first of the other nodes (e.g., an IDnode or master node temporarily operating as an ID node) via the firstcommunication interface to cause the first other node to broadcast oneor more first messages at a first power level, where the first powerlevel is related to a first anticipated range distance.

The first anticipated range distance may be an optimal range for thefirst of the nodes and, in more detail, an optimal range for the firstof the nodes adjusted based upon context data. In even more detail, thefirst anticipated range distance and the second anticipated rangedistance may be adjusted based upon one or more types of context datarelated to how an RF output signal broadcast from the first node may beimpeded.

The node processing unit is also operative to identify which of thenodes associated with the first node have known locations. To do this,the node processing unit may access and review association data storedon the node memory storage (e.g., data indicating what nodes arepassively or actively associated with the first other node), maydetermine which of the remaining other nodes are associated with thefirst other node based upon the reviewed association data, and mayidentify which of the remaining other nodes determined to be associatedwith the first other node have known locations.

The node processing unit is also operative to determine which of theidentified associated nodes received at least one of the first messages,and to communicate another instruction via the first communicationinterface to the first node to cause the first node to broadcast one ormore second messages at a second power level, where the second powerlevel being is to a second anticipated range distance and incrementallysmaller than the first power level.

Finally, the node processing unit is operative to determine which of theidentified associated nodes received at least one of the secondmessages, and then determine a location of the first node to be at orbetween the first anticipated range distance and the second anticipatedrange distance from each of the identified associated nodes that did notreceive at least one of the second messages but received at least one ofthe first messages.

In a further embodiment, the node processing unit may be operative tocommunicate a third instruction via the first communication interface tothe first node to cause the first node to broadcast one or more thirdmessages at a third power level. The third power level is related to athird anticipated range distance and incrementally smaller range thanthe second anticipated range distance. Additionally, the node processingunit may then be operative to determine the location of the first nodeto be at or between the second anticipated range distance and the thirdanticipated range distance from each of the identified associated nodesthat did not receive any of the third messages but received at least oneof the second messages.

In still another embodiment, the node processing unit is able to accountfor movement of the first node with a time interval between instructionssent to the first node. In particular, the node processing unit may befurther operative to communicate another instruction via the firstcommunication interface to the first node to broadcast the secondmessages within a time interval after instructing the first node tobroadcast the first messages. In a more detailed example, the timeinterval may be dynamically set based upon context data related to thefirst node. In even more detail, the time interval may beprogrammatically reduced from a prior value when the context datarelated to the first node indicates the first node is moving (e.g., thefirst node is on a moving conveyor system) and/or the time value of theinterval may be increased from a prior value when the context datarelated to the first node indicates the first node is substantiallystationary (e.g., the node is within a node package recently placed in astorage area).

The node processing unit, in a further embodiment, may be operative torefine the location of the first other node with an updated location ofone or more of the identified associated nodes that did not receive atleast one of the second messages but received at least one of the firstmessages, and cause a second communication interface (e.g., medium/longrange communication interface 485 coupled to processing unit 400) totransmit the refined location to the server.

From a server perspective, FIG. 31 is a flow diagram (similar to FIG.30) illustrating yet another exemplary method for location determinationusing one or more associations of nodes in a wireless node network inaccordance with an embodiment of the invention. Those skilled in the artwill appreciate that while a server may operate to implement the stepsas laid out in method 3000 and discussed above, FIG. 31 provides moredetails as to how a server processing unit (such as processing unit 500running server code 525) may implement such a method at that level ofthe network via method 3100. In this more detailed embodiment, theserver is communicating directly with a master node (e.g., a first node)to direct and control how the master node interacts with and causesoperations to be undertaken on the ID node (e.g., a second node). Thus,step 3105 is similar to step 3005 but more precisely calls forcommunicating with a first node via a communication interface to cause asecond node in the network to broadcast one or more first messages at afirst power level at the request of the first node, where the firstpower level is related to and corresponds with a first anticipated rangedistance. Likewise, step 3120 is similar to step 3020 but more preciselycalls for communicating with the first node via the communicationinterface to cause the second node to broadcast one or more secondmessages at a second power level at the request of the first node, thesecond power level being related to a second anticipated range distanceand incrementally smaller than the first power level. The other steps ofmethod 3100 are similar to those illustrated and explained aboverelative to method 3000, and that the similar principles will apply tomethod 3100.

Those skilled in the art will appreciate that method 3100 as disclosedand explained above in various embodiments may be implemented on aserver (e.g., server 100 in FIG. 5) running one or more parts of servercontrol and management code 525 to direct a master node to controloperations of an ID node (such as ID node F in FIG. 14) as part oflocation determination via ID node advertising. Such code may be storedon a non-transitory computer-readable medium, such as memory storage 515on server 100. Thus, when executing code 525, the server's processingunit 500 may be programmatically transformed to become unconventionallyoperative to perform operations or steps from the exemplary methodsdisclosed above, including method 3100 and variations of that method.

And similar to the node apparatus described above, one embodimentincludes an exemplary server apparatus in a wireless node network thatuses location determination by association. The exemplary serverapparatus generally comprises a server processing unit, server memorycoupled to and used by the server processing unit (e.g., a servervolatile memory and a server memory storage). The server memory storagemaintains at least a program code section, association data, andlocation data. The server apparatus further includes a communicationinterface coupled to the server processing unit and that provides accessto a communication path operatively coupling the server with at least afirst node in the network.

The exemplary server processing unit, when executing at least theprogram code section resident in the server volatile memory, isoperative to perform specific functions or steps. In particular, theserver processing unit is operative to communicate with the first nodevia the communication interface to cause a second node in the network tobroadcast one or more first messages at a first power level at therequest of the first node, where the first power level is related to afirst anticipated range distance; identify which of the remaining nodesin the network associated with the second node have known locations;determine which of the identified associated nodes received at least oneof the first messages; communicate with the first node via thecommunication interface to cause the second node to broadcast one ormore second messages at a second power level at the request of the firstnode, where the second power level is related to a second anticipatedrange distance and incrementally smaller than the first power level;determine which of the identified associated nodes received at least oneof the second messages; and determine a location of the second node tobe at or between the first anticipated range distance and the secondanticipated range distance from each of the identified associated nodesthat did not receive any of the second messages but received at leastone of the first messages. And in a further embodiment, the serverapparatus' processing unit may be further operative to store thedetermined location in the server memory storage as part of the locationdata.

In another embodiment, the server apparatus' processing unit may beoperative to communicate with the first node via the communicationinterface to cause the second node to broadcast the one or more secondmessages within a time interval after communicating with the first nodeto cause the second node to broadcast the one or more first messages. Aspreviously mentioned, this type of time interval may dynamically setbased upon context data related to the second node. Context data mayalso be used as set forth above with respect to the node apparatus butapplied here to the second node—such was where the first anticipatedrange distance is the optimal range for the second node adjusted basedupon context data.

Master Node Location Determination Through Advertise

In another embodiment, a master node may no longer know its location.For example, such a situation may occur when a master node determinesits current location via GPS location circuitry 475, but the master nodefinds itself without access to an adequate number of GPS signals (e.g.,it cannot determine a location due to the lack of a sufficient number ofGPS signals from diverse GPS satellites). Such a situation may happenwhen the master node moves indoors is proximate to a structure thatinterferes with the location signals.

In an exemplary embodiment where a master node attempts to determine itsown location via advertising techniques, the master node may detect aloss of location confidence (e.g., upon a loss of detected GPS signals;upon detecting a separate signal to processing unit 400 indicating themaster node's location is unknown; when processing unit 400 sensesmovement (e.g., via accelerometers (not shown) or the like) but cannotconfirm that the location circuitry 475 is providing updated locationinformation for the node, etc.). In other words, the master node becomesaware that it no longer has a known location.

Next, the master node responds by beginning to broadcast one or moreadvertising messages in a similar way as ID node F 920 f is described asdoing with respect to FIG. 14. This is done so that the master nodehaving an unknown location can advantageously leverage off the knownlocations of nearby other nodes. As such, an embodiment may allow a typeof leveraged chaining effect whereby known locations of particular typesof nodes may be used to extend location information to other nodes thatdo not know their locations (e.g., ID nodes) or nodes that have detecteda loss of location confidence (e.g., master nodes). Thus, such anembodiment may be used to determine an indoor location of a master node(including equipment equipped with master node functionality) in caseswhere signals for the conventional onboard location circuitry 475 arenot available.

Referring back to the exemplary method 3000 and FIG. 30, method 3000 maybe such that the first node is not self-aware of the location of thefirst node. This may happen when the first node (e.g., an ID node) isactually a master node that was previously self-aware of its ownlocation (e.g., via received GPS signals) but is no longer self-aware ofits location (e.g., when the GPS signals can no longer be received),which has the master node changing operation to operate as an ID nodeprior to broadcasting the first message. In other words, the master nodemay no longer be self-aware of its location and begin operating as an IDnode for purposes of location determination prior to broadcasting thefirst message because of a change in the environment surrounding themaster node, such as when the master node has moved inside a structurethat blocks location signals from being received by the master node.Thus, an embodiment may advantageously allow a node to adaptively alteroperations when moving from a clear outdoor environment to an indoorenvironment. And a server may interact with such a master node whilethat master node is operating, for location purposes, as an ID node,temporarily.

Location with Improved RSSI Measurements

In another embodiment, a signal strength measurement between two or morenodes may be used to determine the proximity of the nodes by using oneor more improvements to conventional RSSI measurements. In conventionalRSSI measurements, such as with Bluetooth 4.0, those skilled in the artwill appreciate that adaptive frequency hopping as part of spreadspectrum techniques may cause undesirably cause the signal strength tofluctuate. In other words, the advantage of using frequency hopping andspread spectrum for security and avoidance of interference may have anegative impact on using such signals for stable proximity-basedlocation determinations. Thus, it may be desired to emphasize stabilityof a signal and limits to fluctuation for purposes of locationdetermination.

In one embodiment, a type of improvement for RSSI measurements mayinclude reducing the number of channels and/or a corresponding frequencyrange in use during advertising from nodes. For example, a node may haveprocessing unit 300/400 adaptively control variable power short rangecommunication interface 375/480 to reduce the number of channels and/orthe frequency range used during node advertising. Such a dynamic changemay be implemented, in some embodiments, by altering the content of aparticular type of profile data 330/430, such as an RF profile data thateffectively defines RF characteristics of a node (e.g., frequency, powerlevel, duty cycle, channel numbers, channel spacing, alternativefluctuation modes, etc.). In one further embodiment, a first fluctuationmode may be defined that provides a default or more standardcommunication protocol, such as the conventional frequency hopping,spread spectrum, and channel allocations for Bluetooth® communications.Other alternative modes (one or more) may be defined that alter one ormore RF characteristics to provide increasingly more stable and lessfluctuations of the RF output signal from a node. Thus, a node may bedynamically placed into one or more modes regarding such RFcharacteristics that increasingly emphasize stability of the node's RFoutput signal and limits fluctuation for purposes of enhanced locationdetermination using RSSI measurements.

In another embodiment, a type of improvement for RSSI measurements mayinclude ensuring visibility to and advantageously managing automaticgain control (AGC) circuitry (not shown) that may cause the RF outputsignal to vary for a node. For example, a node may include a type of AGCcircuitry as part of variable power short range communication interface375/480. This type of AGC circuitry may allow node processing unit300/400 or other logic circuitry that is part of variable power shortrange communication interface 375/480 to limit fluctuations undercertain conditions (e.g., when attempting to use RSSI locationdetermination techniques). In this example, different AGC circuitrysettings may be defined in exemplary RF profile data that effectivelydefines RF characteristics of a node (e.g., frequency, power level, dutycycle, channel numbers, channel spacing, alternative fluctuation modes,etc.). This is yet another example of how a node may be dynamicallyplaced into one or more modes regarding such RF characteristics(including AGC circuitry settings) that increasingly emphasize stabilityof the node's RF output signal and limits fluctuation for purposes ofenhanced location determination using RSSI measurements.

Location with Adjustments for Environmental Factors in RF Signal Quality

In general, those skilled in the art will appreciate that environmentalfactors may cause a communication signal, such as an RF signal, tofluctuate or be transmitted and received in a manner that undesirablyvaries depending upon a signal path environment. Passive physicalinterference factors (e.g., forms of electronic signal shielding) may besubstantially close and cause drops in signal strength across the outputranges of the nodes. Additionally, active radio interference factors mayvary across the RF output ranges of the nodes depending upon otheractive devices in the reception vicinity. Thus, the proximateenvironment of a node may have a multitude of adverse factors thatimpact communications and, as a result, the ability to locate the node.

In one embodiment, making location determinations may be enhanced by adata analytics type of approach that may adjust and account fordifferent RF environmental factors for a similar type of node in asimilar type of situation. For example, the quality of the RF outputsignal of a particular type of node and the corresponding physical rangeof that signal to a receiver of known sensitivity may be determined fora given environment. In this example, the system defines a maximum rangeof that signal based on a predetermined condition, such as open-airconnectivity. This may assume an environment with no signal degradationdue to interference or physical shielding. However, both interferenceand physical shielding may diminish the range of the RF output signal ofa node. In a dynamically adaptive and learning manner, the system maycollect information on how a particular type of node may operate in aparticular environment under certain settings (e.g., reported signalstrengths and corresponding settings for RF output signal power levels).This analysis of a similar environment may be repeated. In other words,through such data analytics of an anticipated environment to be faced bya similar node, signal loss information can be generated and applied asa type of context data (i.e., RF data) for a node in a similarenvironment to refine location determination. Thus, an exemplaryembodiment may refine location determinations with adaptive signal losscharacteristics based on a contextual appreciation of an anticipatedenvironment (e.g., physical shielding such as packaging, packagecontents, proximate package, proximate package contents, and physicalinfrastructure causing signal variance) without requiring a calibrationphase.

And advantageously combining those data points with 3^(rd) party datadescribing the physical environment, in which the node was located in atthat time, may refine location even further. Such information may beused as RF data (a type of context data) in future efforts to manage andlocate a similar type of node anticipated to be in a similarenvironment.

In more detail, in an embodiment that refines a location determinationbased upon context and data analytics to adjust for known RFimpediments, the maximum physical range of a node's RF output signalrelative to a receiver of known RF sensitivity is determined. In oneexample, this first range value may be referred to as a theoretical ornominal open-air range of a similar type transmitter-receiver node pairin a similar environment but with substantially no physical shielding orsignal interference negatively impacting the signal range. A secondrange value, which may be considered an actual RF range value, may bethe observed range of the signal in a similar environment but wherethere are contextual factors reducing the communication range, includingphysical shielding due to factors like packaging, package contents,proximate package, proximate package contents, physical infrastructure,interference from other radio sources, or shipper specific informationsuch as vehicle or facility layout information. Through access to priordata analysis of the differing range values and with knowledge of theoperational environment of the transmitting node was in (e.g., a similarenvironment to the proximate environment of the node), a refinedlocation may be determined using an approximation of an actual RF outputrange that intelligently adjusts what may be anticipated to be the RFenvironment of the node. In other words, by knowing the appropriatecontextual environment related to a node (such as signal degradationinformation on how a similar node operates in a similar environment), animproved location determination may be made to make intelligent yetefficient adjustments (such as communication distance adjustments) thatprovide a refined location of the node.

In one example, such as the example shown in FIG. 2, master node 110 bis outside of a container (such as a Uniform Load Device (ULD) container210 known to be used for transporting groups of items on aircraft) thathas an ID node inside the container. A first or theoretical range valuebetween master node 110 b and ID node 120 b may be determined to be 10feet at a specific RF output power level when the package (and relatedID node) may be known to be less than 10 feet away from the scanningnode (e.g., master node 110 b). A second range value at similardistances with similar types of nodes, but with incident RF signal lossas a result of communicating through the wall of the container 210, maybe between 4 and 5 feet. If context data, such as 3^(rd) partyinformation or scan data, indicates the transmitting node is within theULD container 210, the system would expect the transmission range to belimited according to the data analytics associated with this known RFimpediment (e.g., characteristics for transmitting through ULD container210), thus reducing the possible scanning nodes that may see thebroadcasting node within the ULD container, or require the transmittingnode to increase its RF output power to be heard.

FIG. 32 is a flow diagram illustrating an exemplary method for locationdetermination of a first node in a wireless node network based oncontext data in accordance with an embodiment of the invention.Referring now to FIG. 32, method 3200 begins at step 3205 with a networkdevice (such as a master node or server) accessing a first type of thecontext data related to a proximate environment of the first node.

The first type of context data comprises signal degradation informationon how a second node would operate in a similar environment to theproximate environment of the first node when the second node is asimilar type as the first node. Thus, rather than calibrating with anactual measurement relative to the current proximate environment of thefirst node, the signal degradation information provides compensationinformation on what may be generally anticipated in a more generalproximate environment based on how a similar type of node may operate ina similar environment. As the similar environment of the similar node isgenerally an approximation for what is anticipated to be the proximateenvironment of the first node, this advantageously avoids the need foran actual calibration of the proximate environment. In one embodiment,the signal degradation information may be based upon a difference in howthe second node communicates when exposed to an adverse communicationenvironment (such as a similar environment to the proximate environmentof the first node) compared to how the second node would communicateswhen exposed to a nominal communication environment (such as anenvironment that is unencumbered by shielding and interference factors).Those skilled in the art will appreciate that a nominal communicationenvironment need not be perfectly clear of all influences that shield orinterfere with communications.

The types and aspects of signal degradation information may varydepending on a wide variety of factors. In one embodiment, the signaldegradation information may be related to at least one of shielding andinterference. Thus, signal degradation information may include bothpassive and active factors that impact the communication environment.

In another embodiment, the signal degradation environment may be basedupon a degraded operation of the second node when the similarenvironment is an adverse communication environment. In more detail, thesignal degradation information may be based upon a difference in how thesecond node communicates when exposed to the adverse communicationenvironment compared to how the second node communicates when exposed toa substantially normal communication environment, such as an open airenvironment.

In still another embodiment, signal degradation information may relateto at least shipment data for one or more items being shipped (e.g.,currently shipped or shipped in the past) and located in the proximateenvironment of the first node. For instance, a package near the firstnode may include metallic materials that may impede or block RF signalsand the signal degradation information may relate to such informationabout close packages being shipped near the first node. In anotherexample, the signal degradation information may relate to at leastlayout data for one or more physical structures in the proximateenvironment of the first node. In more detail, the layout data may befor one or more physical structures (e.g., walls, machinery, enclosures,and conveyances) in the proximate environment of the node near apredicted path for the first node. In yet another example, the signaldegradation information relates to at least historic data on one or moreanalyzed prior operations of the second node.

At step 3210, the network device, such as a master node or server, mayadjust an anticipated communication distance related to the first nodebased upon on the first type of the context data. In one example, theanticipated communication distance may be a theoretical broadcastdistance based upon parameters of the device's radio. Such ananticipated communication distance is known as it is an estimate of theradio's range. In one example, the adjusted communication distancecomprises an anticipated reduced range distance for a transmission fromthe first node. In another example, the adjusted communication distancecomprises an anticipated reduced receiver sensitivity distance for thefirst node.

In yet another example, adjusting the communication distance may beaccomplished by adaptively adjusting, by the network device, thecommunication distance based upon the signal degradation information anda second type of the context data. In other words, the communicationdistance may be adjusted based upon signal degradation informationconsidered along with other types of context data, such as how the firstnode is being moved (such as an anticipated movement of the first nodealong a predicted transit path for the first node) or a density of othernodes near the first node.

At step 3215, the network device determines the location of the firstnode based upon the adjusted communication distance. In a furtherembodiment, the method may also update the adjusted communicationdistance by the network device based upon movement of the first node,and may refine the location of the first node with an updated adjustedcommunication distance. This may happen with the first node is a mobilemaster node capable of self-determining its own location.

Those skilled in the art will appreciate that method 3200 as disclosedand explained above in various embodiments may be implemented on anetwork device (e.g., exemplary master node 110 a in FIG. 4 or server100 in FIG. 5) running one or more parts of their respective control andmanagement code to perform steps of method 3200 as described above. Suchcode may be stored on a non-transitory computer-readable medium, such asmemory storage 415 on master node 110 a or memory storage 515 on server100. Thus, when executing such code, the respective network device'sprocessing unit may be programmatically transformed to becomeunconventionally operative to perform operations or steps from theexemplary methods disclosed above, including method 3200 and variationsof that method.

In more detail, an exemplary network device apparatus for determining alocation of a first node in a wireless node network based on contextdata, the exemplary network device may include a processing unit, avolatile memory coupled to the processing unit, and a memory storagecoupled to the processing unit. The exemplary network device furtherincludes a communication interface coupled to the processing unit andthat provides a communication path operatively coupling the networkdevice with the first node in the network.

The memory storage for the device maintains at least a program codesection and context data having at least signal degradation information.Such signal degradation information, as a type of context data, isinformation on how a second node would operate in a similar environmentto a proximate environment of the first node when the second node is asimilar type as the first node. Examples of signal degradationinformation may include those discussed above relative to step 3205 ofmethod 3200.

When executing at least the program code section when resident in thevolatile memory, the processing unit of the network device is operativeto perform the steps noted and described above with respect to method3200. In more detail, the processing unit is operative to at leastconnect with the memory storage to access the signal degradationinformation, adjust a communication distance (if needed) related to thefirst node based upon on the signal degradation information, determinethe location of the first node based upon the adjusted communicationdistance, and store the determined location of the first node aslocation data on the memory storage.

Adjusting the communication distance by the processing unit may beaccomplished as described above with regard to step 3210 of method 3200.And as mentioned above, the processing unit may be further operative toadaptively adjust the communication distance where other types ofcontext data are also considered, such as movement and anticipated nodemovement as detailed out above.

In a further embodiment, the network device may be a mobile master nodethat includes location circuitry (such as GPS circuitry 475 of exemplarymaster node 110 a shown in FIG. 4). In this embodiment, the processingof the network device may be further operative to determine a locationof the network device based upon an output signal from the locationcircuitry received by the processing unit, and determine the location ofthe first node based upon the adjusted communication distance and thelocation of the network device. As such, the first type of the contextdata related to the proximate environment of the first node is basedupon the determined location of the first node.

Those skilled in the art will also appreciate that in some operationalenvironments, the signal degradation information may not require anyadjustment to the communication distance in an embodiment. However, inother environments (e.g., adverse RF environments), the signaldegradation information may provide a basis for adjusting thecommunication distance in the embodiment, even if not performed everytime. Thus, an adjustment to the communication distance may not beneeded in all proximate environments of the first node but may beperformed, if needed, based on the proximate environment of the firstnode. It is the ability of an embodiment to adjust this communicationdistance when needed and if needed that advantageously allows forlocating the first node with more accuracy.

Location Through Triangulation

In some embodiments, various methods for determining a node's locationmay rely upon, at least in part, triangulation techniques. In otherwords, as the wireless node network collects data onreceiver-transmitter pairs, other methods for determining location ofthe individual nodes that utilize triangulation, at least in part, maybecome possible. FIG. 15 is a diagram illustrating an exemplary locationdetermination through triangulation within a wireless node network inaccordance with an embodiment of the invention. Referring now to theillustrated embodiment of FIG. 15, three exemplary master nodes M1-M3910 a-910 c are shown with each master node having a known location.Exemplary ID nodes A-E 920 a-920 e are also shown where they are atleast in communication range of one or more of exemplary master nodesMA-M3 910 a-910 c.

In this illustrated example, the master nodes M1-M3 may detect andcollect advertising messages from ID nodes A-E at varying and knownpower levels. The captured information is forwarded by the master nodesM1-M3 to the backend server 100, where location determinations may bemade. For example, factors like RSSI and visibility of each node at eachpower level may be used to determine, with a higher degree of accuracy,the location of nodes where sufficient information is available.

For an exemplary system to triangulate a node, three nodes with knownlocations must have seen the broadcasting node. In this example, twoadvertising ID nodes, A 920 a and B 920 b, were seen by the three nodeshaving known locations (master nodes M1-M3 910 a-910 c). Based upon thecaptured information, the locations of ID node A 920 a and ID node B 920b are calculated.

Chaining Triangulation

In another embodiment, a node with an inferred location may be used withtriangulation techniques to determine a location of another node in awireless node network. FIG. 16 is a diagram illustrating an exemplarylocation determination through chaining triangulation in accordance withan embodiment of the invention. The locations of ID nodes A 920 a and B920 c have been determined by triangulating across master nodes M1-M3,as illustrated in the exemplary embodiment shown in FIG. 15. However, asillustrated in FIG. 16, the location of ID node C 920 c may also bedetermined according to an embodiment.

For example, an exemplary method of determining a node's locationthrough chaining triangulation begins with determining the calculatedlocation of ID node B 920 b (as explained with reference to FIG. 15).Next, a node closer to ID node B 920 b may be used to get the missingthird signal point needed for triangulation. This may be accomplished byplacing ID node B 920 b in a query (scan) mode such that it listens fora message from ID node C 902 c. ID node C is instructed to advertise,thus providing a signal that may be captured by ID node B. Aftercapturing the signal profile of C, ID node B may communicate or sharethe captured information and forward it along to the backend server 100through either of the master nodes M1 or M2. The resulting locationdetermination of ID node C 920 c may have a higher level of positionerror due to it being partially based on a calculated reference (e.g.,the location of ID node B), but the leveraged location determination ofID node C 920 c may be sufficiently accurate (or be an actionablelocation) that useful information may be gleaned about ID node C 920 c.For example, a leveraged or chained location determination of ID node Cmay indicate, with the help of context data, that nodes M1, M2, and IDnode B are all close enough to ID node C that ID node C is determined tobe within the same container nodes M1, M2, and ID node B.

Location Through Proximity to Triangulation (LP2T)

In an embodiment where chaining triangulation may determine locationthrough proximity to triangulation (LP2T), a starting point may bedetermining the relative location of an ID node to a master node basedon the proximity method, as explained above. However, when the relativelocation of the ID node has been determined, a more accurate or refinedlocation of the ID node may be determined based upon the location of allmaster nodes that can capture the RF output signal broadcast from the IDnode, and then triangulating based on observed signal strength of the IDnode. In this example, the proximity-based location is used as an inputin the triangulation calculation to estimate likely signal deteriorationhistorically observed between a node at the proximity-determinedlocation and scanning master nodes. In a further embodiment, by takinginto account historic data on patterns of signal deterioration, a moreaccurate triangulation may be possible, leading to a more accuratelocation determination.

FIG. 33 is a flow diagram illustrating an exemplary method fordetermining a node location using chaining triangulation for one of aplurality of nodes in a wireless node network having a server inaccordance with an embodiment of the invention. Such an exemplary nodelocation need not be precise or exacting, but can be sufficientlyaccurate without absolutes.

Referring now to FIG. 33, method 3300 begins at step 3305 with theserver receiving a location of a first of the nodes from the first node.Next, at step 3310, the server receives a location of a second of thenodes from the second node. For example, with reference to the exampleshown in FIG. 16, master nodes M1 910 a and M2 910 b may transmit theirrespective location coordinates from their respective onboard locationcircuitry to the server so that the server has the current locations ofthese two master nodes.

At step 3315, the server infers a location of a third of the nodes. Forinstance, in the example illustrated in FIG. 16, the server may inferthe location of ID node B 920 b. In one embodiment, inferring maycomprise having the server determine a proximate-based location of thethird node relative to another of the nodes having a known location,such that the proximate-based location operates as the inferred locationof the third node.

In another embodiment, inferring the location of the third node maycomprise having the server determine a relative location of the thirdnode to the first node (as the node having a known location) or to thesecond node (as another node having a known location). Method 3300 mayalso, in another embodiment, include having the server adjust theinferred location of the third node to determine a refined location ofthe third node based upon third node context data related to theinferred location of the third node

At step 3320, method 3300 concludes with the server triangulating thelocation of the one node based upon determined distances to each of thefirst and second nodes, and a determined distance of the one node to theinferred location of the third nodes.

In a more detailed embodiment, method 3300 may triangulate the locationof the one node by accessing first node context data related to acontextual environment near the first node and second node context datarelated a contextual environment near the second node. Such contextualenvironments may include an environment of being on a conveyor system,or within a particular facility, or next to materials that may degradeor shield signals being received by the one node. Next, the moredetailed triangulating may have the server adjust the determineddistance of the one node to the location of the first node based uponthe first node context data to provide a refined distance of the onenode to the location of the of the first node. Then, the server maytriangulate the location of the one node based upon the adjusteddetermined distance of the one node to the location of the first node,the adjusted determined distance of the one node to the location ofsecond node, and a determined distance of the one node to the refinedlocation of the third node.

In a further embodiment, method 3300 may also have the servertransmitting an instruction so as to cause the server to transmit aninstruction to cause the one node to broadcast a plurality ofadvertising signals over a period of time. In such an embodiment, thedetermined distance of the one node to the location of the first nodemay be based upon captured signals from the one node by the first nodeover the period of time and reported to the server by the first node. Inanother embodiment, the determined distance of the one node to thelocation of the second node may be based upon captured signals from theone node by the second node and reported to the server by the secondnode.

In still another embodiment, the server may transmit an instruction tocause the one node to broadcast a plurality of advertising signals atdifferent power levels. In such an embodiment, the determined distanceof the one node to the location of the first node may be based uponcaptured signals from the one node by the first node and reported to theserver by the first node. In another embodiment, the determined distanceof the one node to the location of the second node may be based uponcaptured signals from the one node by the second node and reported tothe server by the second node.

In yet another embodiment, method 3300 may also have the servertransmitting the location information out to a requesting entity (e.g.,another node, a user access device, etc.) upon receipt of a request fora location of the one node from that entity.

Those skilled in the art will appreciate that method 3300 as disclosedand explained above in various embodiments may be implemented on aserver (such as exemplary server 100 as illustrated in FIG. 5) runningone or more parts of a control and management code (such as an code 525)to implement any of the above described functionality. Such code may bestored on a non-transitory computer-readable medium (such as memorystorage 515 in an exemplary server). Thus, when executing such code, aprocessing unit of the server (such as unit 500) may be programmaticallytransformed to become unconventionally operative to perform operationsor steps from the exemplary methods disclosed above, including method3300 and variations of that method.

A server apparatus is also described in an embodiment for determining alocation using chaining triangulation for one of a plurality of nodes ina wireless node network. The server apparatus generally comprises aserver processing unit, a server volatile memory, a server memorystorage, and a communication interface. The server volatile memory,server memory storage, and communication interface are each configuredin the apparatus as coupled to the server processing unit. The servermemory storage maintains at least a program code section and locationdata related to nodes in the network. In some embodiments, the servermemory storage may also maintain context data, such as first nodecontext data and second node context data. The communication interfaceprovides a communication path operatively coupling the server with nodesin the network, such as a first and second node.

The server processing unit, when executing at least the program codesection resident in the server volatile memory, is operative to performvarious functions, such as the functions described in the steps aboverelated to method 3300. In particular, the server processing unit isoperative to receive a request over the communication interface for thelocation of the one node. Based on the request, the server processingunit is then operative to receive the respective locations of the firstand second nodes, and store the locations as part of the location datakept on the server memory storage. The server processing unit is furtheroperative to infer a location of a third of the nodes, and store theinferred location of the third node as part of the location data kept onthe server memory storage. The server processing unit then is operativeto triangulate the location of the one node based upon a determineddistance of the one node to the location of the first node, a determineddistance of the one node to the location of second node, and adetermined distance of the one node to the inferred location of thethird node. And finally, the server processing unit is operative totransmit the location information to the requesting entity over thecommunication interface in response to the request.

In one embodiment, the server processing unit may be further operativeto infer the location of the third of the nodes by being operative todetermine a proximate-based location of the third node relative toanother of the nodes having a known location, where the proximate-basedlocation operates as the inferred location of the third node.

In another embodiment, the server processing unit may be furtheroperative to transmit an instruction over the communication interface tocause the one node to broadcast a plurality of advertising signals overa period of time. In this embodiment, the determined distance of the onenode to the location of the first node may be based upon capturedsignals from the one node by the first node over the period of time andreported to the server by the first node. Alternatively, the determineddistance of the one node to the location of the second node may be basedupon captured signals from the one node by the second node and reportedto the server by the second node.

In another embodiment, the server processing unit may be furtheroperative to transmit an instruction over the communication interface tocause the one node to broadcast a plurality of advertising signals atdifferent power levels. In such an embodiment, the determined distanceof the one node to the location of the first node may be based uponcaptured signals from the one node by the first node and reported to theserver by the first node. Alternatively, the determined distance of theone node to the location of the second node may be based upon capturedsignals from the one node by the second node and reported to the serverby the second node.

In yet another embodiment, the server processing unit may be furtheroperative to infer the location of the third node by being operative todetermine a relative location of the third node to the first node or,alternatively, to the second node.

In still another embodiment, context data may be relied upon to refinelocations. More specifically, the server processing unit may be furtheroperative to adjust the inferred location of the third node to determinea refined location of the third node based upon third node context datarelated to the inferred location of the third node.

In a more detailed embodiment, the server memory storage may furthermaintains context data, and the server processing unit may be furtheroperative to triangulate by being operative to access first node contextdata as part of the context data maintained on the server memorystorage, where the first node context data is related to a contextualenvironment near the first node. Likewise, the server processing unitmay be further operative to access second node context data as part ofthe context data maintained on the server memory storage, where thesecond node context data is related a contextual environment near thesecond node. The server processing unit may then be operative to adjustthe determined distance of the one node to the location of the firstnode based upon the first node context data to provide a refineddistance of the one node to the location of the of the first node. Assuch, the server processing unit may be operative to triangulate thelocation of the one node based upon the adjusted determined distance ofthe one node to the location of the first node, the adjusted determineddistance of the one node to the location of second node, and adetermined distance of the one node to the refined location of the thirdnode.

Combined Methods for Determining Node Location

In light of the examples explained above for locating a node, oneskilled in the art will appreciate that a further embodiment expresslycontemplates using more than one of the above-described locationdetermination techniques when determining a refined location of a nodein a wireless node network. For example, such combination embodimentsmay apply an ordered or prioritized approach whereby a first locationtechnique is applied to generate first location information regardingthe location of a node in the wireless network. Thereafter, a secondlocation technique may be selected from a hierarchy or prioritized setof techniques (some of which may work better in certain circumstancesand be chosen or dynamically prioritized based upon the contextualenvironment), and applied to generate second location informationregarding the location of the node or refining the location of the node.Other embodiments may apply additional location techniques to generatefurther refined location information.

In an embodiment, the information in the exemplary hierarchy generallyidentifies which technique may be preferred to be used initially as wellas a ranked grouping or listing of when to apply other locationtechniques. Such information in the exemplary hierarchy may be fixed(based upon successful historic data and experience) or be dynamicallyaltered over time as nodes may move relative to each other and, forexample, based upon context data that provides more information relativeto the a current or anticipated contextual environment.

Applying Node Location Determination in a Vehicular Environment

The various exemplary methods and techniques described above fordetermining the location of a node provide an advantageous way to locatea node. However, further embodiments may advantageously apply suchmethods and techniques in a vehicular environment when dealing withlogistics operations where a node is to be located in a vehicle, movedwithin a vehicle, or removed for delivery from a vehicle.

Essentially, embodiments may use a package enabled with a node(generally referred to as a node package or node-enabled package) toship one or more items and such a node package may be advantageouslyplaced, located, moved, or removed for delivery in avehicle/transportation/shipping/logistics environment. As explainedthroughout this description, a node package is generally a package to beshipped that is related to a particular node. The node and the relatedpackage travel together as part of the shipping process. In a generalembodiment, the node may simply be within the package. In anotherembodiment, the node may be attached to the package (e.g., adhered to aninterior portion of the package, fixed to a part of the package whereone or more status indicators of the node may be visible through thepackage, etc.). In another embodiment, the node of the node package maybe part of the package or the packaging materials used to comprise anexterior, interior, or separating/cushioning material within the nodepackage. In more detail, the node may be integrated as part of thepackage or packaging materials (e.g., integrated as part of a pallet, aULD container, a corrugated fiberboard box, and the like). In stillanother detailed embodiment, the node of the node package may be fullyor partially embedded within the package or packaging materials used tohelp form a general container, which maintains an item to be shippedalong with the node.

FIG. 20 is a diagram illustrating exemplary node packages located in anexemplary vehicle environment in accordance with an embodiment of theinvention. Referring now to FIG. 20, exemplary vehicle 9300 isillustrated as an example of a general mobile logistics transport orconveyance carrying packages being shipped. Those skilled in the artwill appreciate that vehicle 9300 may be implemented as various types oflogistics conveyances (e.g., automobile, delivery van, autonomousvehicle, truck, trailer, train, aircraft, marine vessel (ship), etc.).Within exemplary vehicle 9300, packages may be placed, stored, andorganized within different storage devices or units, such as storageunit A 9305 or storage unit B 9310. In general, a storage device or unithelps to maintain one or more packages in a configuration that helps toassure save shipment, minimize damage to the packages, and provide a wayto organize what is being stored. Different embodiments of a storageunit may store a single package or may storage a wide variety ofdifferent types of packages that use different types of packagingmaterials (e.g., corrugated fiberboard boxes, wooden and non-woodenpallets, containers, etc.) and in large numbers.

Vehicle 9300 includes a vehicle master node 9315—an exemplaryimplementation of a master node, such as master node 110 a shown anddescribed with respect to FIG. 4. Vehicle master node 9315 is shownoperative to communicate with server 100 over a longer-rangecommunication interfaces (such as interface 485 on exemplary master node110 a) and operative to communicate with other nodes, such as masternode 9320 associated with storage unit A 9305, master node 9325associated with storage unit B 9310, and other nodes associated withparts of such storage units and node packages stored within the storageunits. In more detail, each storage unit may include, in someembodiments, built-in nodes associated with particular shelves, lockers,receptacles, or other parts of the particular storage unit.

Thus, an exemplary storage unit (such as storage unit A 9305) may be anode-enabled storage unit used within a logistics vehicle to safely andintelligently transport node packages. As such, the exemplary storageunit may itself have a hierarchy of nodes (e.g., a master node, and oneor more other nodes (ID nodes or other master nodes) assigned todifferent parts of the unit) and be operative to detect the location ofparticular node packages via the various location determination methodsdiscussed herein as the node package is placed in a storage locationwithin the unit, moved between storage locations of the unit or betweendifferent units, or simply removed from the storage location within theunit.

As shown in FIG. 20, various node packages 9330 a-9330 d may be kept indifferent storage locations of storage unit A 9305 within vehicle 9300.Similarly, other node packages 9330 e-9330 g are kept in portions ofstorage unit B 9310. Such node packages may be placed into particularstorage locations according to shipping information related to the nodepackages. For example, the node packages may be placed into particularstorage locations according to weights of the particular node packages,a planned loading scheme (such as according to an anticipated deliveryschedule), to storage capacity of the particular different locationswithin the storage unit, or according to a storage type for theparticular different locations (e.g., one location for storing envelopetypes of packages, another location for storing boxed container type ofpackages, another location for storing containerized packages (e.g.,ULDs), etc.).

Shipping of containerized groups of packages (e.g., ULD types ofcontainers made to optimize airborne logistics handling of packages) isan example of where a mobile storage unit (such as a movable unit loaddevice (ULD)) may be deployed when shipping node packages in an airborneenvironment. FIG. 21 is a diagram illustrating exemplary mobile storageunits, such as ULDs, used as containers that help ship node packages inan exemplary airborne environment in accordance with an embodiment ofthe invention. Referring now to FIG. 21, a cut-away perspective view ofan exemplary aircraft fuselage 9400 is illustrated. In particular, anexemplary floor 9405 of a cargo storage area within fuselage 9400 isshown having multiple roller elements that help facilitate movement ofcargo within the cargo area. Additionally, while not shown in FIG. 21,the cargo storage area and floor 9405 typically include structure andfastening points to help hold any cargo loaded within fuselage 9400. Thecargo storage area within exemplary fuselage 9400 may be split into anupper area and a lower area by an additional floor 9410.

The cut-away perspective example illustrated in FIG. 21 shows a lowercargo area where various ULD containers 9420 a-9420 d are shown alongwith an airborne master node 9415, which is (depending on the aircraft'slocation and communication mode and status) operative to communicatewith server 100—much like vehicle master node 9315 does as shown in FIG.20. In general, the illustrated configuration of ULD containers 9420 a-dis used similar to the storage units illustrated and described in FIG.20. For example, each ULD container 9420 a-d may have different storagelocations within it and one or more master nodes (not shown) dedicatedand attached internally so that they may track, monitor, and communicatewith different node packages loaded within the ULD as well as othernodes and a server—much like the master node 9320 for storage unit A9305 can track, monitor, and communicate with different node packagesloaded within the storage unit as well as other nodes and server 100.Node packages within each ULD may communicate with nodes in the ULD andmay communicate directly with airborne master node 9415 directly (orindirectly through other master nodes within the ULD). And as such,shipping information may be used when the node packages are placed intoparticular storage locations within a particular ULD according toweights of the particular node packages, a planned loading scheme forthe ULDs (such as according to an anticipated delivery schedule), tostorage capacity of the particular different locations within the ULD,or according to a storage type for the particular different locations.

In light of the exemplary vehicular environments shown in FIGS. 20 and21 showing structure used when initially placing, storing, maintaining,locating, moving, and eventually removing a node package for delivery,those skilled in the art will appreciate that each of the embodimentsdescribed above related to methods for locating a node may be furtherenhanced when applied to an exemplary vehicular environment. Forexample, in one embodiment, determining a node's location may furthercomprise determining a location of the node-enabled package within avehicle to be the location of the node. In a more detailed embodiment,the method that determines a node location may further generate alocation message regarding where the node-enabled package is locatedwithin the vehicle based upon the determined location of the node. Sucha message may be displayed to a user (e.g., logistics personnel thathandle packages being shipped) on a user interface of a node or useraccess device operating as a node (e.g., smartphone or smart wearabledevice). For example, such a displayed message may be a type of aninformed prompt (“Pickup Package X at Storage Location 01 in StorageUnit A”) or strategic instruction (“Place Package X in Storage Location01 in Storage Unit A”) or (“Move Package X at Storage Location 01 inStorage Unit A to Storage Location 03 in Storage Unit B”). In someembodiments, the network device or node that determines the node'slocation may also provide such a display to the user, but in otherembodiments, the location message may be transmitted to another node fordisplay to the user.

In another embodiment, an exemplary method that determines a node'slocation may also access shipping information related to thenode-enabled package and generate a relocation message regarding wherethe node-enabled package may be relocated within the vehicle based uponthe determined location of the node and the accessed shippinginformation. Such a message may be displayed to a user similar to thelocation message described above—namely, that such a relocation messagemay be displayed to a user (e.g., logistics personnel that handlepackages being shipped) on a user interface of a node or user accessdevice operating as a node (e.g., smartphone or smart wearable device)and that in some embodiments, the network device or node that determinesthe node's location may provide such a display to the user, but in otherembodiments, the relocation message may be transmitted to another nodefor display to the user.

In more detail, the shipping information may comprise weight informationon the node-enabled package that is used in determining where torelocate or initially place the node-enabled package.

In another embodiment, such shipping information may be used to create aloading scheme to help organize where to locate or relocate thenode-enabled packages. Thus, the location or relocation of thenode-enabled package within the vehicle may be determined according to aloading scheme. In more detail, such a loading scheme may be related toan anticipated delivery schedule, where the node-enabled package may beplaced within or removed from the vehicle according to the anticipateddelivery schedule.

Logistics Applications of a Wireless Node Network

As described above, an exemplary wireless node network may be useful ina logistics application where an item is to be located. Further, such anexemplary wireless node network may also be useful in logisticsapplications where the item is moving between locations, and the networkprovides an enhanced level of visibility and management of the itemwithin such a logistics environment. In other words, an embodiment of anexemplary wireless node network in accordance with one or moreprinciples of the present invention helps enable enhanced logisticaloperations that manage information when shipping and tracking an item.FIG. 17 is a diagram illustrating an example logistics operation usingexemplary components of a wireless node network in accordance with anembodiment of the invention.

Logistics Beyond Pickup and Delivery

Referring now to FIG. 17, an ID node 120 a is illustrated as beingdeployed and associated with an item (e.g., package 130) to be shipped.As the package 130 is being prepared for shipping 1700, and is intransit as part of shipment 1705, and is in the possession of theintended recipient 1710, components of an exemplary wireless nodenetwork are deployed to manage information regarding the shipment duringthese three phases.

In a general example of using a wireless node network for managinglogistics related to an item to be shipped, a shipping customer mayinitially register the item (such as package 130) with a node (such asan ID node) to be shipped from an origin location to a destinationlocation. One or more management hand-offs of the item and node occursas the item and the ID node collectively transit a path from the originto the destination. Each hand-off may be based upon an awareness of theshipment path the ID node associated with package 130 will take as it istransferred through a shipping path from its origin to destination.Hand-off of the package 130 and ID node are managed and coordinated withmaster nodes (such as master nodes 110 a-110 h), which are managed byserver 100, along the anticipated shipment path. During operation alongthe shipping path, server 100 receives information and updates fromnodes, manages and authorizes hand-offs between different nodes, andtracks information related to current associations, shared data, sensordata available, locations of the nodes, and context data that helps torefine the location of nodes. Thus, with the ID node associated withpackage 130, the visibility of the package 130 may be extended for thecustomer beyond the conventional custodial control during transit 1705as the shipping customer prepares the item for shipment 1700 prior to aninitial drop-off and after delivery of the item to the recipient 1710.

In a more detailed embodiment, an exemplary method for managinglogistics related to an item to be shipped using a wireless node networkbegins with registering a node with the item to be shipped. For example,the shipping customer may control user access device 200, and use device200 to initially associate an ID node 120 a and package 130 with atracking number as part of preparing to ship the package 130 (a type ofitem). In one embodiment, device 200 may use a particular app or otherprogram module resident and operating on device 200 to input thetracking number of the package 130. Device 200 then provides thatinformation back to server 100 via network 105 to associate the trackingnumber with the package 130 and ID node 120 a. Device 200, in someembodiments, may then print a label for the shipment of package 130 (andID node 120 a). In another embodiment, ID node 120 a may be apreprogrammed node with pre-existing shipping and payment relatedinformation associated with it. Further details of a label-less shippingand payment in another embodiment are described below.

Concurrent with this action, the shipping customer may associate ID node120 a with package 130. For example, the shipping customer may place theID node 120 a within package 130 and, in some cases, physically attachthe ID node 120 a to a particular part of package 130. In anotherexample, the shipping customer may place an exterior label on package130 where the label itself includes ID node 120 a. Other examples mayeffectively group ID node 120 a with package 130 within a largerpackage, container, or pallet of items or packages that collectivelytravel together.

In this manner, device 200 may operate as a type of master node undercontrol of the app or other program module, and be associated with thepackage 130 and ID node 120 a from an association managementperspective. For example, device 200 may operate via the app or otherprogram module along with Bluetooth® hardware and software working ondevice 200 to communicate with ID node 120 a. Other embodiments may relyon other short-range communication interfaces for device 200 tocommunicate with ID node 120 a. And in one embodiment, device 200 mayreceive one or more security credentials from server 100 in order toconnect and actively pair or connect with ID node 120 a.

With at least the shipping information at the server 100, server 100 maydetermine a predicted shipping path for the package 130. In oneembodiment, server 100 may have historic data indicating an optimalroute for shipping an item from point A to point B that uses aparticular shipping path (e.g., pick-up near A by a particular courier,transport by vehicle to a particular facility, further transport viaaircraft to another facility near point B, and transport by vehicle tofacilitate delivery by a courier at point B). In one example, thepredicted path may only be for a portion of the route between twopoints, such as an origin point and a destination point.

In a further example, the predicted path (or part thereof) may beadjusted based on the contextual environment of an item being shipped.For instance, depending on context data (such as weather information,historic data on success for particular transit segments, capacityinformation for third party carriers, etc.), server 100 may alter theinitially predicted shipping path to provide a refined predictedshipping path that is more optimized under the current conditions andcontext. This allows the server 100 to further anticipate which masternodes may be used along an anticipated shipping path (or refinedshipping path), to help efficiently manage shipment of the package 130to point B. Those skilled in the art will further appreciate that anembodiment may only partially identify what master nodes may be usedalong the anticipated shipping path (or refined shipping path), and thatfurther master nodes may be identified as the package 130 is actively inroute to point B depending on context data (e.g., master nodeavailability, weather information, etc.).

In a more detailed example, server 100 may use sort data analytics topredict an appropriate shipping path along which the package 130 and theID node 120 a will travel, identifying predicted master nodes the IDnode 120 a will be within range of during its journey. In the exampleflow illustrated in FIG. 17, nodes 110 a-110 h refer to different masternodes along an exemplary predicted shipping path, which includes atleast a pick-up and drop-off of ID node 120 a and package 130 at anorigin and destination, respectively.

In one example, the shipping customer may place package 130 and itsassociated ID node 120 a in a drop box or repository for items to beshipped. In the illustrated example of FIG. 17, drop box is representedas drop node 110 a. Essentially, drop node 110 a may be implemented witha type of master node connected to or integrated into a drop box orlocker unit type of logistics repository (more generally referred toherein as a node-enabled logistics receptacle). As the shipping customerphysically places ID node 120 a into drop node 110 a, device 200 mayhand-off ID node 120 a to drop node 110 a, update server 100 with thisassociation information, and disassociate from ID node 120 a. In thismanner, the system has visibility into the status and location of anitem (such as package 130) prior to pick-up from drop node 110 a.Further details of an exemplary node-enabled logistics receptacle aredescribed below.

At the drop node 110 a, a courier may pick-up the package 130 and IDnode 120 a. The courier has a courier node 110 b, which knows thetracking number and associated ID node 120 a at time of pickup, or looksup the ID node 120 a MAC address based on a captured tracking number(part of information broadcast or advertised by ID node 110 a.Basically, the master node responsibility transfers to or is otherwisehanded off to courier node 110 b, which now acts as a master nodeactively connected and associated with ID node 120 a (by virtue ofcommunications from courier node 110 b back to server that authorizesthe association of ID node 110 a with courier node 110 b anddisassociates drop node 110 a with ID node 110 a).

Similar handoffs occur between different master nodes and ID node 120 aoccur as package 130 and ID node 120 a transit the anticipated shippingpath in accordance with instructions sent to different master nodes byserver 100. In one embodiment, associations are accomplished during suchhandoffs with security credentials requested, authorized, andtransmitted to the appropriate master node. In another embodiment,associations are merely passive associations that do not require activeand authorized pairings. Yet, the passive association still may allowthe system to keep track of ID node 120 a and package 130 as theytransit the anticipated shipping path.

New associations (active and passive) and disassociations are updated toserver 100. And server 100 may change programming in different nodes aspackage 130 and ID node 120 a transit the shipping path—such as changingthe operation of a master node (such as ULD node 110 e) to shift tooperating as an ID node while airborne or when GPS signals are lost. Inanother example, certain mobile types of node may have responsibilitieschanged to wired types of nodes as a way of preserving the power of amobile type of node. If ID node 120 a fails to associate for a certaininterval and needs to be reacquired, ID node 120 a may update its statusflag to a particular Alert Stage and may attempt to communicate with anincreasingly broader range of master nodes in order to be found.

During the transit, server 100 may share information with differentnodes, such as context data, timer/clock data, environmental data, etc.Sensor data from the ID node 120 a may be gathered via scans from amaster node, and then forwarded back to server 100. And as server 100manages the associations, handoffs, and information going to and comingfrom ID node 120 a (via master nodes), server 100 is able to determinethe location of ID node 120 a using one or more of the various locationdetermination techniques described above. As such, server 100 is able toprovide information related to the ID node 120 a and its related package130 in response to requests for such information.

When package 130 and ID node 120 a arrive at the destination (e.g.,point B), courier node 110 h may update server 100 once ID node 120 a isplaced at the destination and disassociated with courier node 110 h.However, visibility need not end at such a drop-off event (such asarriving at the destination). The recipient customer's user accessdevice 205 may act as another master node, and associate with ID node120 a after delivery. In one example, server 100 is notified by couriernode 110 h that delivery has been made. Thereafter, server 100 maynotify device 205 with this information. In response, an app or otherprogram module on device 205 may cause device 205 to operate as a nodeand to actively seek association with ID node 120 a. When device 205 andID node 120 a connect and are given authorization by server 100 toactively associate, server 100 is notified and may provide furtherinformation to device 205 (e.g., sensor data, etc.) and may be able todetermined updated location data about ID node 120 a and package 130after delivery has occurred. In another example, active association maynot be needed between device 205 and ID node 120 a as status informationmay still be gathered by device 205 via passive association, where thestatus information provides further visibility regarding the ID node 120after delivery to the destination.

FIGS. 18 and 19 are flow diagrams illustrating various exemplary methodsfor managing a shipment of an item using a wireless node network, suchas that illustrated in FIG. 17. Referring now to FIG. 18, exemplarymethod 1800 begins by transmitting shipping information to the server toregister the ID node and the item to be shipped at step 1805 andassociating the ID node to a first master node related to a predictedpath for shipping the item at step 1810. At step 1815, the server isupdated to reflect the association between the ID node and the firstmaster node. Typically, this may come in the form or a communicationfrom the first master node to the server. When the first master node isa user access device (e.g., one of a laptop computer, a desktopcomputer, a tablet device, a personal area network device, a smartphonedevice, and a smart wearable device) that is operated by a shippingcustomer, the server may be updated to become aware that the ID node isassociated with the first master node prior to a pick-up event in thepredicted path.

For example, a shipping customer may use their smartphone to entershipping information and register that the ID node and the item (such aspackage 130) are to be shipped from an origin point to a destinationpoint. Prior to when the item and ID node are picked up by an initialcourier (e.g., from a drop box, locker unit, or other receptacle), theshipping customer's smartphone operates as the first master node and isassociated with the ID node. As such, and with an update to the server,the server now has visibility into the status and location of the IDnode prior to a pick-up event in the predicted shipping path from theorigin point to the destination point.

The method 1800 may continue at step 1820 by disassociating the ID nodeand the first master node when associating the ID node and a secondmaster node related to the predicted path as the ID node transits thepredicted path. In one example, the ID node need not disassociate withthe first master node commensurate with associating with the secondmaster node. Thus, those skilled in the art will appreciate that the IDnode may be associated with one or more master nodes at a given point intime and may be selectively disassociated with certain master nodesdepending on the need for the ID node to securely share data withdifferent master nodes.

At step 1825, the server is updated to reflect the disassociationbetween the ID node and the first master node (if that has occurred yet)and the association between the ID node and the second master node asthe ID node continues to transit the predicted path. At step 1830, themethod may associate the ID node to a third master node near an end ofthe predicted path for shipping the item, and then at step 1835 notifiesthe server to reflect the association between the ID node and the thirdmaster node.

In the method 1800, associating the ID node to the third master node instep 1830 may be performed after a drop-off event in the predicted path.The method may also rely upon context data to adjust for anenvironmental aspect of the predicted path when associating the ID nodeto any of the first, second, or third master nodes.

For example, after the item and ID node are delivered to or near thedestination, the recipient's smartphone may operate as the third masternode associated with the ID node. Data, such as sensor data, may beshared with the recipient while the recipient's smartphone operates asthe third master node associated with the ID node. As such, and with anupdate to the server, the server now has visibility into the status andlocation of the ID node after a drop-off event.

Thereafter, the recipient may unregister the ID node and item given theitem is now in the recipient's possession and control. For example, therecipient may remove the ID node from the item (e.g., the package 130),deactivate the ID node to otherwise power down the device, update theserver regarding the deactivated status of the ID node (and thedisassociation of ID node and the third master node), and then clean upand/or recharge the ID node for future use in shipping another item.

Method 1800 may also include receiving context data related to thepredicted path. In one embodiment, such context data may advantageouslyallow for adjustments due to one or more environmental aspects of thepredicted path when associating the ID node to any of the master nodes.For example, the context data may include scan data indicating the typeof material in package 130 (the item), which may cause RF shieldingissues with the ID node.

Referring now to FIG. 19, exemplary method 1900 is explained from theperspective of the server, which can authorize certain types of nodeassociations. The server may be updated, in some embodiments, withassociation information when an ID node and a master node are passivelyassociated. In such a situation, the nodes have not established anauthorized association where they can securely share data. However, asmethod 1900 explains in more detail, an embodiment may manage a shipmentof an item when active associations are established.

Method 1900 begins with the server receiving shipping information toregister the ID node and the item to be shipped in step 1905. The method1900 then provides a first set of authentication credentials (e.g.,security pin information) to a first master node to permit the ID nodeto associate with the first master node related to a predicted path forshipping the item at step 1910. In one example, the first master nodemay be a user access device, such as a laptop computer, a desktopcomputer, a tablet device, a personal area network device, a smartphonedevice, or a smart wearable device. And step 1920 may be performed priorto a pick-up even in the predicted path.

At step 1915, the server receives an update to reflect the associationbetween the ID node and the first master node. The method 1900 thenprovides a second set of authentication credentials to a second masternode to permit the ID node to associate with the second master node anddisassociate the ID node from the first master node as the ID nodetransits the predicted path at step 1920. At step 1925, the server thenreceives an update to reflect the association between the ID node andthe second master node as the ID node continues to transit the predictedpath (or a portion of a predicted path). When the ID node and the firstmaster node disassociate, the server may also be updated.

In some examples, the method 1900 may have the server provide a thirdset of authentication credentials to a third master node to permit theID node to associate with the third master node as the ID node reachesan end of the predicted path for shipping the item at step 1930. In someexamples, this step may be performed after a drop-off event in thepredicted path.

Finally, at step 1935, the server receives a notification that reflectsthe association between the ID node and the third master node. When theID node and the second master node disassociate, the server may also beupdated.

In method 1900, another embodiment has the server providing any of themaster nodes with context data related to an environmental aspect of apart of the predicted path. For example, exemplary context data mayinclude layout data related to a facility in which the ID node is movingbetween master nodes. In more detail, the received context data may berelied upon to adjust for an environmental aspect of the predicted pathwhen associating the ID node to any of the first, second, or thirdmaster nodes.

In still another embodiment, method 1900 may also determining a locationof the ID node based upon association information received by the serverand location information related to at least one of the first, second,or third master nodes.

As previously discussed, the server may predict a transit route from afirst point to a second point along at least a portion of the predictedpath for shipping the item. In one example, the first point is an originand the second point is a destination point with both being identifiedin the shipping information of the item. However in other examples, thefirst and second point along a predicted path may merely be interimpoints without encompassing the originating shipment point or theultimate destination of the item being shipped. Further, another examplemay adjust the predicted path as the ID node transits the path. In thisway, the server may adapt based upon, for example, context data, so asto optimize or at least account for a changing contextual environmentwhen managing the shipment of an item.

In another embodiment, a non-transitory computer-readable medium isdisclosed that contains instructions, which when executed on a processor(e.g., processor 500 of server 100), performs another embodiment of amethod for managing a shipment of an item using a wireless node networkhaving at least one ID node, a plurality of master nodes, and a server.In this embodiment, the exemplary method begins with the serverreceiving shipping information to register the ID node and the item tobe shipped. The method predicting a first portion of a transit route forthe item from a first point to a second point. For example, a firstpoint may be the origin point and the second point may be thedestination point—both of which are identified in the shippinginformation. In another example, the first and second points are any twopoints along the transit route. Furthermore, the transit route may bepredicted as a series of portions or segments that may use particulartypes of master nodes during transit (e.g., master nodes used by aparticular courier for pick-up, an anticipated vehicle used by thepickup courier, one or more anticipated facilities that may be used bythe vehicle, an anticipated air route (e.g., an anticipated departingairport, an anticipated aircraft, anticipated types of containers suchas a type of ULD or pallet used on the aircraft, and an anticipatedarriving airport), a facility near the anticipated arriving airport, avehicle used to carry the item, and a courier that may deliver the itemat the destination point). Those skilled in the art will realized thatsome of the potential portions of an exemplary predicted path or transitroute may be relatively simple for a local delivery, or may be quitecomplex from an intermodal perspective when the origin point anddestination points are very far away from each other.

Next, the method authorizes a first master node to associate or connectwith the ID node near the origin point. This may be done prior to apick-up event for the ID node and item being shipped. For example, whenthe first master node is a user access device (e.g., a laptop computer,a desktop computer, a tablet device, a personal area network device, asmartphone device, and a smart wearable device) for the shippingcustomer, visibility as to the status and location of the ID node may beextended to prior to a pick-up event. In one embodiment, such anauthorization is performed by the server 100 when it receivesinformation from the first master node regarding the ID node, determinesthat the first master node and the ID node should be actively paired andassociated, and the server 100 sends the appropriate security pininformation as a type of authorization credentials that permit the firstmaster node to actively pair and connect with the ID node. After thefirst master node is associated with the ID node, the server receives anupdate reflecting the association.

Next, the server may authorize a second master node to associate withthe ID node as management responsibility of the ID node is handed offfrom the first master node to the second master node at the second pointon the predicted transit route. In one embodiment, the method mayauthorize the first master node to disassociate with the ID node.However, in other embodiments, the first master node may stay associatedwith the ID node—even after the ID node is authorized to associate withthe second master node. The server then receives an update to reflectthe association between the ID node and the second master node as the IDnode continues on the predicted first portion of the transit route.

The method may further authorize the second master node to disassociatewith the ID node and a third master node to associate with the ID nodeas management responsibility of the ID node is handed off from thesecond master node to the third master node near the destination pointon the predicted transit route. This may be done prior to a pick-upevent for the ID node and item being shipped. For example, when thethird master node is a user access device (e.g., a laptop computer, adesktop computer, a tablet device, a personal area network device, asmartphone device, and a smart wearable device) for the recipient,visibility as to the status and location of the ID node may be extendedto after a drop-off event. After the third master node is associatedwith the ID node, the server receives a notification to reflect theassociation between the ID node and the third master node.

And during the method, the server may determine a location of the IDnode based upon association information received by the server andlocation information related to at least one of the first, second, orthird master nodes. As discussed above, various techniques are availablefor locating a node and, in some cases, adjusting for adverse RFenvironmental conditions with context data to more accurately refine thelocation of a node. As such, the server keeps track of the location ofnodes in the wireless node network, and may provide that information (aswell as other types of shared or sensor information) when requested andauthorized to do so.

From a system perspective of such a logistics application of a wirelessnode network, an exemplary system is disclosed for managing a shipmentof an item using a wireless node network. With reference to FIG. 17, theexemplary system generally comprises an ID node (such as node 120 a), aplurality of master nodes (such as nodes 110 a-110 h), and a server(such as server 100). The ID node is registered to the item (such aspackage 130) being shipped. Each of the master nodes are predicted to belocated at a different part of an anticipated transit route for the itemas the item is shipped from an origin point to a designation point ofthe anticipated transit route. Each of the master nodes is operative tocommunicate with the ID node over a short-range communication path, andoperative to communicate with other master nodes and the server 100.

The server operates to track and report a location of the ID node and alocation of the master nodes. As shown in FIG. 17, server 100 relies onnetwork 105 to communicate with different master nodes (110 a-110 h) aswell as user access devices 200, 205 that may operate and function as amaster node associated with ID node 120 a at certain times. Aspreviously discussed, server 100 may employ a variety of differenttechniques (or a combination of different techniques) for determiningthe location of ID node 120 a or one of the other nodes in the network.

The server is also operative to facilitate the transfer of managementresponsibility of the ID node between different master nodes as the IDnode moves along the anticipated transit route. For example, asdiscussed above, nodes communicate via broadcast and scanning methods,and may be associated under control of the server 100 as part ofmanaging the wireless node network. In this way, a first of the masternodes may be associated with the ID node prior to a pick-up event forthe ID node and item to be shipped. In one example, user access device200 may operate as a master node and be associated with ID node 120 aprior to being placed into drop node 110 a and picked up by a courierfrom the receptacle related to that drop node 110 a.

Later, a second of the master nodes may be associated with the ID nodeafter the ID node is disassociated with the first of the master nodes atan intermediate point of the anticipated transit route. And, a third ofthe master nodes may be associated with the ID node after a drop-offevent for the ID node and item to be shipped. For example, user accessdevice 205 may operate as a master node and be associated with ID node120 a after the ID node 120 a and item are dropped off at an intendeddestination point (e.g., a type of drop-off event).

In an embodiment of the system, each of the master nodes may beoperative to update the server upon completing a disassociation orassociation with the ID node. This provides the server with associationinformation with which it can use to manage and track the nodes in thewireless node network. When associating nodes, the server may beoperative to transmit a set of authorization credentials to one of themaster nodes and the ID node to authorize a desired association betweenthe master node and the ID node. The server may also be operative todetermine the location of the ID node based upon context data, such asinformation relating to an environmental aspect of a part of theanticipated transit path (e.g., RF shielding aspects of the item beingshipped with the ID node or a container holding the ID node, buildinglayout information, etc.).

Those skilled in the art will readily appreciate that operations of suchan exemplary wireless node network, as set forth herein, are not limitedto tracking just a package, but may be used to manage logistics andtracking of other types of items, such as an object or a person. Indeed,some embodiments provide enhanced capabilities that facilitate bettertracking of items, objects, and people as they move to a morerestrictive indoor environment, by using a low power ID node inadvertising mode in the presence of one or more master nodes.

Additional Node Enhancements & Improved Implementations

In light of the above description covering elements of an exemplarywireless node network and how they may be used to help locate and trackitems, further embodiments may enhance and improve how such elementscommunicate. For example, additional embodiments explained in moredetail below describe nodes that may use self-adjusting broadcastsettings, nodes that may deploy enhanced multi-component radios toimprove how a node listens for other nodes and/or detects the locationof other nodes, as well as enhanced communication management techniquesdeployed with a system of nodes faced with a congested node landscapethat otherwise makes for difficult node-to-node control andcommunication exchanges. Still further embodiments focus on multiplefeatures and aspects of a specialized container-centric type of node,which may deployed in such exemplary wireless node networks as part of alogistics container, such as a ULD or other logistics receptacle. FIGS.34-99 help explain these further embodiments that enhance and improvelocating, monitoring, and delivery management and are particularlyuseful in shipping, logistics, and transportation field applicationsusing exemplary components of a wireless node network in accordance withvarious embodiments of the invention.

Power Profile Enhancements

As explained above, a node may operate in an exemplary wireless nodenetwork in accordance with a profile, such as a broadcast profile storedas profile data 330 in memory of the ID node or profile data 430 inmemory of a master node. Profile data (such as data 330 or 430) is atype of data that is typically provided to the node and kept in volatileand/or non-volatile memory of the node as data defining a typeoperational behavior or parameters used for a particular operationalbehavior for the node in the network. The node may use such profile databy being instructed by a separate managing device to change operationalbehavior in accordance with the profile data.

However, additional embodiments involving may have a speciallyprogrammed node (such as an ID node or master node or other types ofnodes) that can self-direct and self-adjust characteristics of its ownoperation according to profile data (such as how to broadcast anadvertising signal according to a broadcast profile defining a set oflow, medium, and high power levels to use at particular times) withoutrequiring instructions from a managing device to change operationalbehavior. Such embodiments, for example, may self-adjust a broadcastsetting based on self-detected events (generally referred to asbroadcast monitoring events). Those network elements observing theself-adjusting node may become informed of the self-adjusting node'supdated value for its broadcast setting from the signal header, whichcreates improved management efficiency as observing/managing nodes avoidthe need to constantly send instructions to the self-adjusting node tochange operational settings (such as output power level, frequency, ortiming of the broadcasted advertising message emanating from theself-adjusting node under an updated or changed setting).

FIG. 34 is a diagram illustrating an exemplary enhanced self-adjustingwireless node system in accordance with an embodiment of the invention.Referring now to FIG. 34, an exemplary network of interrelated andinteracting elements are shown configured as an exemplary system 3400,which includes server 100, master node 34110 a, network 105 thatprovides a data connection between server 100 and master node 34110 a,and finally several ID nodes (i.e., ID node 34120 a, ID node 34120 b)that are each connected to the master node 34110 a. As shown in FIG. 34,ID node 34120 a is disposed within package 34130 along with an itembeing shipped 34150 such that ID node 34120 a may be associated with theitem being shipped 34150 and tracked/monitored by master node 34110 a assuch. In other embodiments, ID node 34120 b may also be similarlydisposed within a package and associated with an item being shipped.Furthermore, in still other embodiments, exemplary system 3400 mayinclude multiple master nodes (similar to master node 34110 a) andadditional ID nodes in configurations similar to, for example, thatshown in FIG. 2.

In contrast to the ID nodes illustrated in FIGS. 1-4, ID node 34120 aand ID node 34120 b are shown as specially programmed to useself-adjusting broadcast code (such as 34325 a and 34325 b), whichenables the respective ID node to make use of one or more onboardbroadcast profiles (such as 34330 a and 34330 b) when autonomouslyself-adjusting to change or otherwise alter how the node broadcastsmessages based on self-detected broadcast modification events. Whilemaster node 34110 a is not shown having the self-adjusting broadcastcode and related onboard broadcast profiles similar to those shown forID nodes 34120 a and 34120 b, those skilled in the art will appreciatethat as explained in more detail below, master node 34110 a may bedeployed within an embodiment of system 3400 to also be self-adjustingwith one or more broadcast profiles.

In general, exemplary system 3400 may, for example, operate with ID node34120 a detecting a type of broadcast modification event (such asdetecting proximity to a conveyor structure or an elapsed time sincecapturing barcode data with onboard sensors). Based on thisself-detected event, ID node 34120 a may then access broadcast profile34330 a within the node's memory, determine an updated value for thenode's broadcast setting based on the detected event, and self-adjustthe node's broadcast setting using the updated value without relyingupon a broadcast setting instruction message from master node 34110 a.Such an operation of system 3400 may take place, for example, whenpackage 34130 is placed on the conveyor structure that moves package34130 (and ID node 34120 a) closer and closer to master node 34110 a. Asa timer on ID node 34120 a counts down from when the ID node 34120 a hasbeen placed on the conveyor, ID node 34120 a may detect the end of aparticular time period, which then causes the ID node 34120 a todynamically and autonomously self-adjust the node's own broadcastsetting that alters its RF transmission output power level, frequency,or timing related to what the ID node 34120 a is to be broadcastingduring a next time period. As such, ID node 34120 a may operate as asystem component that autonomously self-adjusts the output power ofbroadcasted advertising messages, how often the node broadcasts suchmessages, or the frequency of such broadcasted advertising messages (ora combination of like types of broadcast setting changes). To accomplishsuch self-adjusting broadcast functionality, the node's broadcastprofile 34330 a has settings that may be defined for continuouslychanging settings (e.g., gradually changing on a smooth increase ordecrease) and/or changing in discrete steps (e.g., incrementallychanging from a current value to an updated value). Thus, a node (suchas an ID node, master node that also has location circuitry, or othertypes of nodes described herein that can be deployed in a wireless nodenetwork) may employ a self-detecting and self-adjusting scheme ofhardware, data, and software instructions or code to manage how the nodeis broadcasting without imposing further overhead burdens on a managingdevice in the network that normally controls and manages the node as itoperates within the network. FIGS. 35 and 36 explain further details ofsuch a node and how it operates.

In more detail, FIG. 35 provides a diagram illustrating further aspectsof an exemplary ID node 34120 a that uses self-adjusting broadcast code34325 a and at least one broadcast profile 34330 a as part of the system3400 shown in FIG. 34 in accordance with an embodiment of the invention.Referring now to FIG. 35, those skilled in the art will appreciate thatID node 34120 a includes many of the same hardware, code, and datacomponents as shown for exemplary ID node 120 a of FIG. 3. As such,similar functionality exists for what is numbered the same and describedabove regarding exemplary ID node 120 a of FIG. 3. Notably, theembodiment with exemplary ID node 34120 a illustrated in FIG. 35 deploysnode control and management code 325 (as stored in memory storage 315and loaded for execution by processing unit 300 in volatile memory 320)and self-adjusting broadcast code 34325 a. In some embodiments,self-adjusting broadcast code 34325 a may be implemented as anintegrated part of node control and management code 325, such as aprogrammatic function or program module within code 325. But in otherembodiments, self-adjusting broadcasting code 34325 a may be implementedseparately from code 325.

In general, exemplary self-adjusting broadcast code 34325 a coordinatesthe self-detection of broadcast modification events feedback fromvarious elements within ID node 34120 a, accesses one or more broadcastprofiles 34330 a, and enables the autonomous self-control and adjustmentof how the node's communication interface 375 operates to broadcastadvertising messages using updated broadcast settings pursuant to thebroadcast profile 34330 a in response to the detected broadcastmodification events. In embodiments where there are multiple broadcastprofiles 34330 a resident in memory 315/320, self-adjusting broadcastcode 34325 a determines which communication profile to use (e.g., indoorbroadcast profile, congested landscape broadcast profile, an outdoorbroadcast profile, an airborne broadcast profile, and the like). Thismay, in some embodiments, be based on sensor data 350, shared data 345(such as location data and context data relevant to the ID node),association data 340, and the like that provide insight on the ID node'scommunication environment and allow for a proactive selection of adesired communication profile to file such an environment.

In one embodiment, the broadcast profile 34330 a may be established as atype of “ranging” profile that defined different output power levels invarious ways. For example, the ranging profile may have a firstbroadcast setting (e.g., power level) for an initial range commensuratewith a first time period elapsing after crossing a reference point orcommensurate with a location of the node being proximate a firststructure relatively near the reference point. As time goes on andfurther broadcast modification events are sensed or otherwise detected,a second broadcast setting may be used for a second range relative tothe reference point, and so on. In a further embodiment, ID node 34210 amay calibrate itself as it uses self-adjusting broadcast code 34325 aand broadcast profiles 34330 a by using captured barcode data at knownlocations with known distances to reference points (e.g., the locationof master node 34110 a).

FIG. 36 is a flow diagram illustrating an exemplary method forself-adjusting a broadcast setting of a node, such as ID node 34120 a,in a wireless node network in accordance with an embodiment of theinvention. Referring now to FIG. 36, method 3600 begins at step 3605with the node detecting a broadcast modification event. In general, abroadcast modification event may be considered as an event sensed ordetected by the node itself reflecting a relevant change in theoperating environment of the node. For example, an embodiment may use atime-based event as the detected broadcast modification event. As such,in some embodiments, the current value of the broadcast setting may beused during a first time period according to the broadcast profile whilethe detected time-based event reflecting a broadcast modification eventmay comprise an end of that first time period. In other embodiments, thebroadcast profile may define multiple time profile segments wheredifferent values of the broadcast setting are being applied by the nodebased upon a detected time or timer value. In more detail, a detectedbroadcast modification event may be a detected time-based eventreflecting an end of a first time profile segment within a pluralitytime profile segments defined by the broadcast profile. The broadcastsetting defined per the broadcast profile during each time profilesegment may reflect a constant or changing profile during the respectivetime profile segment.

In a further embodiment, the broadcast modification event may comprisean association-based event detected when the node associates withanother node in the wireless node network. For example, as discussedabove relative to FIGS. 9 and 10, exemplary nodes (including ID node34120 a, ID node 34120 b, and master node 34110 a) arecharacteristically able to establish associations or logicallyconnection relationships between each other where such associations aretypically server-authorized and tracked as part of managing thedifferent network elements in the wireless node network. Extending thistype of association functionality to the nodes depicted in exemplarysystem 3400 shown in FIG. 34, an embodiment of ID node 34120 a maybecome associated with the master node 34110 a as the ID node 34120 a(and its related package 34130 and item 34150) moves within range of themaster node 34110 a and after the server 100 directs the two nodes toassociate (with authorization). As a result, information identifying therelationship between ID node 34120 a and master node 34110 a may beprovided to server 100 and may be provided, as some point, to each of IDnode 34120 a and master node 34110 a. Thus, exemplary association data340 may exist in volatile memory 320 and/or memory storage 315 of IDnode 34120 a as a type of data identifying associations between nodes.Similar association data may exist within the memory of master node34110 a.

Another type of potential broadcast modification event may be alocation-based event detected when the node is mobile andself-determines its present location to be proximate to a structure. Asshown in FIG. 4, exemplary master node device 110 a includes locationcircuitry 475 (such as GPS circuitry or other positioning circuitry)that allows the master node to self-determine its location. Furthermore,as described above, context data 560 may be provided by server 100 tothe master node (such as master node 34110 a) where the context dataprovides information related to different structures (e.g., a particulartype of courier device, vehicle, facility, transportation container,etc.). Exemplary master node 34110 a may leverage these same master nodefeatures to self-determine its present location to be proximate to astructure, as well as be deployed as a mobile type of node (such as amaster node mounted within a vehicle or aircraft). Thus, detecting suchlocation-based information by a similarly equipped master node may beconsidered a type of detected broadcast modification event under afurther embodiment of method 3600.

Further still, the broadcast modification event in another embodimentmay comprise a sensor-based event detected when a sensor on the nodedetects a change in an environmental condition. As shown in FIG. 34 aswell as FIGS. 3 and 4, the nodes described herein may include sensorsthat generate sensor data, such as sensor data 350 in ID node 34120 a orsensor data gathered by other nodes. Sensor data 350 may exist involatile memory 320 and/or memory storage 315 as a type of data recordedand collected from an onboard sensor or from another node and mayreflect a change in an environmental condition. For example, sensor data350 may include temperature readings from a temperature sensor onboardan ID node (or data 450 from a sensor onboard a master node) and/orhumidity readings from a humidity sensor in another node. Thus, when anonboard sensor detects a change in an environmental condition using asensor deployed on the node, such a sensor-based event may be a type ofdetected broadcast modification event in an embodiment of method 3600.

And, in yet another embodiment, method 3600 may implement step 3605where the detected broadcast modification event may comprise acombination of at least two from the group consisting of a time-basedevent, an association-based event, a location-based event, and asensor-based event. As such, different embodiments of method 3600 maydetect the broadcast modification event as more than one self-detectedreflecting a type of change for the detecting node where the node mayoperate more efficiently or in a desired manner by switching itsbroadcast setting.

Method 3600 continues at step 3610 with the node accessing a broadcastprofile stored within the node's memory in order to determine an updatedvalue for the broadcast setting of the node based upon the detectedbroadcast modification event. Then, at step 3615, method 3600 has thenode self-adjusting the broadcast setting of the node from a currentvalue to the updated value.

For example, as shown in FIG. 35, processing unit 300 of exemplary IDnode 34120 a may access a broadcast profile 34330 a when executing step3610. For an embodiment where multiple broadcast profiles 34330 a arestored within profile data 330, a further embodiment of step 3610 mayalso include first determining which of the broadcast profiles to use asthe desired broadcast profile. In other words, an embodiment maymaintain different communication profiles for the node and firstdetermine which of the communication profiles to use as the broadcastprofile when accessing the appropriate profile when determining theupdated value for the broadcast setting. Further still, an embodimentmay access the broadcast profile to determine the updated value afterdetecting the broadcast modification event and without being promptedwith an instruction from a second node (such as master node 34110 a) toadjust the broadcast setting.

In step 3610, the broadcast setting may be implemented as an RFtransmission output power level setting identified as part of thebroadcast profile of the node. In another embodiment, the broadcastsetting of the node may be a frequency setting identified as part of thebroadcast profile of the node. In yet another embodiment, the broadcastsetting of the node may be a timing setting identified as part of thebroadcast profile of the node. Further still, other embodiments maydeploy a node having multi-variate broadcast settings as part of thenode's broadcast profile (e.g., different broadcast settings that arebased on two or more of RF transmission output power level, frequency,and/or timing settings that collectively adjust how the node broadcastssignals).

In more detail, the updated value of the broadcast setting, asdetermined in step 3610, may be implemented in a variety of ways. Forexample, the updated value may generally be implemented as one ofmultiple broadcast setting values maintained as part of the broadcastprofile of the node. In some embodiments, the current value and theupdated value of the broadcast setting for the node may be within arange defined by the node's broadcast profile of the node. In anotherembodiment, the updated value may be a changed broadcast setting wherethe change may, for example, relate to a period of time defined by thebroadcast profile of the node. Further still, another embodiment mayhave the updated value for the broadcast setting being a change to atleast one of a modified RF transmission output power level setting forthe node as defined by the broadcast profile; a modified frequencysetting for the node as defined by the broadcast profile; and a timingsetting for the node as defined by the broadcast profile.

Additionally, the determined updated value for the broadcast setting mayrelate to structure in or near the operating environment of the node. Inone embodiment, the updated value may be determined to as apredetermined value related to a structure in proximity to the nodewhere the predetermined value is part of context data maintained in amemory storage of the node. For example, a ULD may be in proximity to IDnode 34120 a as the ULD may contain the package 34130 within which theID node 34120 a has been placed. As such, the ID node 34120 a maydetermine the updated value for the broadcast setting to be apredetermined increase in RF transmission output power level relative tothe proximity of the ULD (which may otherwise shield and attenuatesignals broadcasted from ID node 34120 a). In another embodiment, theupdated value may be implemented as a predetermined value related tostructure (such as a shipment receiving building) associated with amaster node in the wireless node network. In more detail, an embodimentmay implement the updated value as a default broadcast value related toan interior of a shipping container associated with the master node(such as when a master node is fixed to an interior of the shippingcontainer so as to monitor and communicate with ID nodes deployed inpackages maintained within the shipping container).

Method 3600 may continue in some embodiments to step 3620, where thenode broadcasts a message to a managing device in the network (such as amanaging master node) using the updated value of the broadcast settingand where a header of the message reflects the updated value. In moredetail, the node (e.g., ID node 34120 a) may broadcast a message withone or more advertising signals intended to be received by the devicemanaging the broadcasting node (e.g., master node 34110 a) where aheader of the message (such as the header of the exemplary advertisingmessage packet depicted in FIG. 7) updates the managing device about theupdated value of the broadcast setting of the node (the updated value ofthe TX Power Level part of the header).

The nodes used in method 3600 may include an ID node and a master node(fixed or mobile), or a container node. In particular, such an ID nodedeployed as the self-adjusting node of method 3600 may be capable ofcommunicating directly with a master node but incapable of communicatingdirectly with a server in the wireless node network. Another embodimenthas the node comprising a master node capable of self-locating,communicating directly with the ID node over a first communication path,and communicating directly with a server over a second communicationpath distinct from the first communication path. If the master node isat a fixed location, there may be little need for self-locatingcircuitry in the master node—thus, an embodiment may have the node beinga fixed location master node that communicates directly with an ID nodeover a first communication path, and separately communicates directlywith a server over a second communication path distinct from the firstcommunication path. Further, an embodiment may have the node deployed asa container node associated with a particular container and capable ofcommunicating directly with an ID node over a first communication path,communicating directly with a server over a second communication pathdistinct from the first communication path, but incapable ofself-locating due to a lack of location circuitry.

Those skilled in the art will appreciate that method 3600 as disclosedand explained above in various embodiments may be implemented on a node(e.g., master node 34110 a, ID node 34120 a, or a container nodeattached to a logistics container used to temporarily maintain items orpackages) running one or more parts of node control and management code325 or 425 that includes a self-adjusting broadcast code module. Suchcode may be stored on a non-transitory computer-readable medium, such asmemory storage 315 on ID node 34120 a or memory storage on master node34110 a. Thus, when executing code 325 (or code 425 if on a masternode), the respective node's processing unit may be programmaticallytransformed to become unconventionally operative to perform operationsor steps from the exemplary methods disclosed above, including method3600 and variations of that method.

A further embodiment of an exemplary self-adjusting broadcasting nodeapparatus (such as the ID nodes and master node illustrated in FIGS. 34and 35) running such code as part of a wireless node network, mayinclude at least a node processing unit, a memory storage, acommunication interface, and detector circuitry. In this embodiment, thememory storage, communication interface, and detector are each coupledto the node processing unit. For example, as shown in FIG. 35, ID node34120 a has memory 315, memory 320, and variable power short rangecommunication interface 375 coupled to processing unit 300. Further, thesensors 360 and timer 370 (each being examples of detector circuitry)are shown being operatively coupled to processing unit 300.

The memory storage (such as memory 315) in this exemplary self-adjustingbroadcasting node apparatus maintains self-adjusting broadcast code(such as self-adjusting broadcast code 34325 a) for execution by thenode processing unit along with at least a broadcast profile (such asone of broadcast profiles 34330 a). The communication interface in theembodiment is operative to communicate with a second device (e.g., an IDnode or master node) in the wireless node network in accordance with thebroadcast profile. As part of this embodiment, the detector circuitry isoperative to generate data (e.g., time-based data, location-based data,and/or sensor-based data) related to a relevant broadcast modificationevent deemed important enough to have the node apparatus react withself-adjustments to how it broadcasts.

In more detail, the node processing unit of the embodiment operates toexecute the self-adjusting broadcast program code section, which thencauses the node apparatus to become specially programmed to control andperform the steps and operations as described above relative to method3600 and variations of that method described above that transform thenode apparatus in a non-conventional and innovative manner. Morespecifically, an embodiment may have the node processing unit beingoperative, when running such a self-adjusting broadcast program codesection to specially adapt the apparatus, to receive the generated datarelated to the broadcast modification event from the detector; accessthe broadcast profile in the memory storage; determine an updated valueof a broadcast setting for the communication interface according to thebroadcast profile and based upon the generated data related to thebroadcast modification event; self-adjust the broadcast setting from acurrent value to the updated value without receiving an adjustmentinstruction on the communication interface from the second device in thewireless node network; and cause the communication interface to operatein accordance with the updated value of the broadcast setting.

In further embodiments, the broadcast setting may comprise an RFtransmission output power level setting, a frequency setting, or atiming setting identified as part of the broadcast profile (e.g., one ofbroadcast profiles 34330 a). Further still, in some embodiments, thebroadcast setting may be implemented as a combination of two or more ofan RF transmission output power level setting, a frequency setting, or atiming setting identified as part of the broadcast profile.

The values in the broadcast profile for such broadcast settings may alsobe implemented in a variety of forms. For example, the updated value forthe broadcast setting as accessed within the memory storage may compriseone of several different broadcast setting values maintained as part ofthe broadcast profile on the memory storage. In such an example, theupdated value may be a lower RF power level compared to the current RFpower level. In another example, the current value and the updated valuemay be implemented as different values within a range defined by thebroadcast profile on the memory storage. The updated value, in someembodiments, may be a change to the broadcast setting that relates to aperiod of time defined by the broadcast profile. Further still, anotherembodiment may have the updated value be one or more of a modified RFtransmission output power level setting for the communication interfaceas defined by the broadcast profile, a modified frequency setting forthe communication interface as defined by the broadcast profile, and atiming setting for the communication interface as defined by thebroadcast profile. For example, ID node 34120 a may have one ofbroadcast profiles 34330 a that defines different values for power,timing, and frequency settings with which to use when causing thecommunication interface 375 to broadcast advertising signals tocommunicate with other nodes.

In another embodiment, the memory storage may maintain context datarelated to an environment of the node apparatus. Such context data, asexplained above, may include information related to different structures(e.g., a particular type of courier device, vehicle, facility,transportation container, etc.) in the general vicinity proximate to thenode or in an anticipated environment for node as the node apparatusmoves from location to different location. As such, the updated valuefor the broadcast setting may be implemented as a predetermined valuerelated to a structure in proximity to the node apparatus (such as aconveyor system that is moving the node apparatus). Such a predeterminedvalue may be a part of the context data maintained in the memory storageof the node apparatus.

In more detail, an embodiment may have the updated value for thebroadcast setting being a predetermined value related to a structure,where the structure is associated with a master node as the seconddevice in the wireless node network. For example, the master node may bededicated to a storage facility or to a mobile delivery van or to ashipping container. When the structure is a shipping containerassociated with the master node, the updated value may be a defaultbroadcast value related to an interior of that particular shippingcontainer. In this way, the node apparatus may self-adjust its broadcastsetting to stop broadcasting for a time period while within the shippingcontainer or may self-adjust its broadcast setting to a higher RFtransmission output power level to account for the shielding orattenuation characteristics related to the shipping container.

As noted above, a node's memory storage may include multiple broadcastprofiles (such as profiles 34330 a shown in FIG. 35). Thus, as part ofan embodiment, the node processing may be further operative, whenexecuting the self-adjusting broadcast code (such as code 34325 a), todetermine one of the multiple communication profiles as the broadcastprofile to use. For example, one profile may be used for airbornetransportation situations where the node apparatus has been loaded on anaircraft and is in the processing of being transported where anotherprofile may be used for storage situations when the node apparatus istemporarily stored within a larger storage facility prior to pickup fordelivery as part of a package. Indeed, yet another profile may bededicated for use while in a mobile delivery situation where the nodeapparatus and its associated package and item being shipped (such aspackage 34130 and item 34150). As such, an embodiment may deploydifferent broadcast profiles depending on location, movement status, orrelevant shipping phase (e.g., initial activation with the package, dropoff, loading/unloading related to transport vehicles or containers,hand-off between custodians, airborne transport, land-based transport,sorting, storage, mobile delivery, post-delivery reporting, and thelike).

Further embodiments may include more details on what is then broadcastedin accordance with the updated value of the broadcast setting. Forexample, in one embodiment, when the node processing unit causes thecommunication interface to operate in accordance with the updated valueof the broadcast setting, the communication interface is controlled bythe node processing unit to broadcast a message in accordance with theupdated value such that a header of the message reflects the updatedvalue. Such a message may be broadcast for reception by a managingdevice (e.g., a master node such as node 34110 a) where the header ofthe message updates the managing device about the updated value of thebroadcast setting of the node. For example, the header of thebroadcasted message from the communication interface 375 of ID node34120 a may include a flag or other data bit/byte or information relatedto the updated value (such as an updated value of the TX Power Levelflag as shown in exemplary advertising package 700 in FIG. 7).

As discussed above, the node processing unit is operative to receivedata related to the broadcast modification event as generated by thedetector. Further detailed embodiments may provide further specificityon characteristics of different types of detectors that sense or detectbroadcast modification events that, once detected, indicate it is timeto self-adjust the broadcast setting. For example, in one embodiment thedetector may be implemented as timer circuitry (such as timer 370),which operates to generate the data related to a time-based broadcastmodification event. More specifically, such a time-based event may adetected end of a first time period where prior to the end of the firsttime period, the node processing unit is operative to cause thecommunication interface to operate in accordance with the current valueof the broadcast setting before moving to the updated value after theend of the first time period. In another embodiment, the broadcastprofile may define multiple time profile segments where the time-basedbroadcast modification event may be the end of a first of the timeprofile segments. As such, the node processing unit is operative tocause the communication interface to operate in accordance with thecurrent value of the broadcast setting during the first time profilesegment, and then self-adjust the broadcast setting to an updated valueduring the next of the time profile segments.

In another embodiment, the detector may be implemented with a sensorcoupled to the node processing unit (or interface circuitry incommunication with and logically considered part of the node processingunit). Such a sensor is generally operative to sense an environmentalcondition proximate to the node apparatus as the generated data relatedto the broadcast modification event. As such, a sensor-based broadcastmodification event may be detected and relevant data is captured orgenerated by the sensor when the sensor detects a threshold change inthe environmental condition. For example, as shown and discussedrelative to ID node 34120 a, sensors 360 may be used as a type ofdetector that generate data related to a broadcast modification event,such as at least a threshold change in temperature, humidity, light,motion, impact, or other environmental condition relative to the nodeapparatus.

In still another embodiment where the node apparatus may be implementedwith a master node (such as master node 34110 a), the detector may beimplemented with location circuitry (such as GPS circuitry 475 as shownand explained relative to FIG. 4 or other types of location circuits,proximity sensors, or distance detectors). Such location circuitry isgenerally coupled to the node processing unit and can determine acurrent location of the node apparatus as the generated data related tothe broadcast modification event. In some embodiments, the data on thecurrent location may be a coordinate location while other embodimentsmay generate data on the current location in terms of relative location(e.g., 5 feet from a wall, ground, ceiling, or other structure). In moredetail, the broadcast modification event may be considered alocation-based event detected when the node processing unit determinesthe node apparatus is located proximate to a structure based upon bothcontext data maintained on the memory storage (a type of informationabout an anticipated operating environment for the node apparatus) andthe current location of the node apparatus (a type of information aboutthe actual operating environment for the node apparatus).

In some embodiments, the node apparatus may deploy multiple types ofdetectors (e.g., a timer, location circuitry, or sensors) so that abroadcast modification event may include a combination of at least twoof a time-based event, a location-based event, and a sensor-based event.Thus, more complex embodiments may use different types of detectors todetect a relevant modification event as well as use multi-facetedbroadcast profiles with broadcast settings having different types ofvalues for different characteristics of how the communication interfacemay be self-adjusted to operate.

As described above, the node apparatus may be implemented as differenttypes of node devices. For example, in one embodiment the node apparatusmay be implemented as an ID node (such as ID node 34120 a), which iscapable of communicating directly with a master node (such as masternode 34110 a) as the second device over the communication interface butincapable of communicating directly with a server in the wireless nodenetwork. As such, the ID node apparatus may be at a low level of thewireless node network, with the master node at a middle level, and theserver being at top level within the network.

In another embodiment, the node apparatus may be implemented as a masternode. In this embodiment, the detector is implemented with locationcircuitry (such as GPS circuitry) coupled to the node processing unitand operative to determine a current location of the master node as thegenerated data related to the broadcast modification event. Thus, thedetected broadcast modification event may be a location-based type ofevent when the node apparatus is implemented as a master node. In moredetail, the node apparatus implemented as a master node may furtherinclude an additional communication interface. In particular, the nodeapparatus may include a server communication interface coupled to thenode processing unit and operative to communicate directly with a serverin the wireless node network over a network communication path (inaddition to the communication interface that communicates with thesecond device in accordance with the broadcast profile). As such, thecommunication interface that communicates with the second device does soover a short range communication path with an ID node as the seconddevice. Such a short range communication path is distinct from thenetwork communication path used by the server communication interface.

Further still, an embodiment where the node apparatus may be implementedas a master node may be implemented with a fixed location master node ata mid-level of the wireless node network. Such a fixed location masternode (while not requiring location circuitry) may also have a servercommunication interface coupled to the node processing unit andoperative to communicate directly with a server in the wireless nodenetwork over a network communication path (similar to that describedabove).

And in still another embodiment, the node apparatus may be attached toor otherwise associated with a container used at least to temporarilymaintain items (such as a container or ULD that may temporarily storepackage 34130 that includes ID node 34120 a and item 34150). Asdiscussed in more detail below, such an exemplary container node may beimplemented as the node apparatus as attached or associated with thecontainer and having a server communication interface coupled to thenode processing unit and operative to communicate directly with a serverin the wireless node network over a network communication path (again,similar to that described above for the master node).

These different embodiments of an exemplary node apparatus that are eachself-adjusting with respect to broadcast settings of its broadcastprofile may be used or deployed within a system level embodiment. Forexample, an exemplary embodiment of an enhanced self-adjusting wirelessnode system may generally include at least two node apparatus devicesthat interact with each other in an unconventional and innovativemanner. In particular, the first node apparatus in the system isoperative to at least (a) self-adjust a broadcast setting for the firstnode apparatus to an updated value in response to a detected broadcastmodification event and based upon its broadcast profile, and (b)broadcast a message in accordance with the updated value of thebroadcast setting such that the message has at least header informationreflecting the updated value. The first node apparatus may self-adjustthe broadcast setting to the updated value without being prompted by thesecond node apparatus to adjust the broadcast setting.

The system's second node apparatus is then operative to receive themessage from the first node apparatus and store data from the messageassociated with the first node apparatus as well as the updated valuebased upon the header information in the received message. Such headerinformation allows the second node apparatus to become aware of thechanged or self-adjustment made by the first node in response to thedetected broadcast modification event.

In more detail, the broadcast setting of the first node apparatus in theexemplary system may be an RF transmission output power level setting, afrequency setting, and/or a timing setting identified as part of thebroadcast profile of the first node apparatus. In other words, theupdated value may be a change to the broadcast setting where the changecomprising one or more from a group consisting of a modified RFtransmission output power level setting for the first node apparatus asdefined by the broadcast profile, a modified frequency setting for thefirst node apparatus as defined by the broadcast profile, and a timingsetting for the first node apparatus as defined by the broadcastprofile. Explained in with respect to still another embodiment, theupdated value for the first node apparatus may be a change to thebroadcast setting where the change may be implemented as a combinationof two or more from a group consisting of a modified RF transmissionoutput power level setting for the first node apparatus as defined bythe broadcast profile, a modified frequency setting for the first nodeapparatus as defined by the broadcast profile, and a timing setting forthe first node apparatus as defined by the broadcast profile.

Further, the updated value for the broadcast setting may be one ofmultiple broadcast setting values maintained as part of the broadcastprofile for the first node apparatus, or may be implemented as anupdated value within a range defined by the broadcast profile for thefirst node apparatus.

As explained above relative to method 3600 as well as embodiments of theexemplary node apparatus, an embodiment of the system may have the firstnode apparatus detecting specific types of broadcast modification eventsthat are relevant enough to network operations to warrantself-adjustment of how the first node communicates. For example, thebroadcast modification event may be a time-based event detected by thefirst node apparatus at an end of a first time period during which thefirst node apparatus broadcasts in accordance with a current value ofthe broadcast setting. In another example, the broadcast modificationevent may be an association-based event detected when the first nodeapparatus associates with a second device in a wireless node network(such as when the second device (e.g., an ID node) is the second nodeapparatus in a managing device approved association relationship withthe first node apparatus).

In still another example where the first node apparatus includeslocation circuitry to self-determine location (e.g., when the first nodeapparatus is a master node, such as node 34110 a), the broadcastmodification event may be a location-based event. Such a location-basedevent may be detected when the first node apparatus moves and thelocation circuitry self-determines a present location of the first nodeapparatus to be proximate to an anticipated structure (such as a storagearea, a conveyor system, a delivery vehicle, or a logistics receptacle).

In another example, the first node apparatus may include at least onesensor that monitors an environmental condition relative to anenvironment of the first node apparatus. As such, the broadcastmodification event may be a sensor-based event detected when the sensoron the first node apparatus detects a change in the environmentalcondition (such as a change in temperature, humidity, light, etc.)relative to the first node apparatus.

Further still, a system embodiment may have the first node apparatusdetecting the broadcast modification event as a combination of at leasttwo from the group consisting of a time-based event, anassociation-based event, a location-based event, and a sensor-basedevent.

Specialized Container Node

As discussed above, embodiments of different elements of the exemplarywireless node networks allow for deployment of a hierarchical network ofelements useful in enhanced shipping operations. Generally, the elementsdescribed above fall within a few different hierarchical levels of thenetworks—namely, with an ID node at a first level of the network and aserver at the top level of the network while a master node may bedeployed at a middle level of the network. However, in additionalembodiments, an enhanced exemplary wireless node network may include afurther type of node element integrated with, attached to, or otherwiseassociated with a type of logistics container (such as a ULD used whentransporting items on an aircraft, a trailer capable of being moved by atruck, a train car capable of being moved on a railway system by alocomotive, an intermodal shipping container capable of being moved onat least two different types of transportation modalities, and thelike). This further type of node element is generally referred to as acontainer node. Further embodiments may deploy such a container node tofacilitate enhanced system scanning capabilities that leverage off usingthis type of container node in addition to fixed facility nodes, alongwith localized scanning, and more intelligent and efficient use of thehierarchy of network elements to accomplish scanning for package IDnodes in order to better handle the congestion issues anticipated. Asexplained below, FIGS. 37-39 illustrate exemplary systems that deployone or more container nodes and illustrate further details of anexemplary container node while FIG. 40 illustrates steps from anexemplary method performed by such a container node when operating tohelp manage at least a part of a multi-level wireless node network.

In more detail, FIG. 37 is a diagram illustrating an exemplary enhancedlogistics system for managing a multi-level wireless node networkinvolving a plurality of packages in different containers in accordancewith an embodiment of the invention. Referring now to FIG. 37, exemplarysystem 3700 is illustrated as including server 100 connected to facilitymaster node 37110 a through network 105. Those skilled in the art willappreciate that facility master node 37110 a may be similarlyconstructed and programmed as explained above relative to master node110 a (and as shown in FIG. 4). As shown in FIG. 37, facility masternode 37110 a is operative to wirelessly communicate with node-basedelements within each of container A 37100A, container B 37100B,container C 37100C, and container D 37100D. Containers A and B are shownas being separate and distinct from each other, while containers C and Dare shown in a nested relationship. Each of containers A-D typicallymaintain, at least temporarily, items or packages being shipped or othercontainers maintaining one or more items or packages. As shown, thecontainers A-D may be one or more types of logistics containers. Inother words, the system 3700 as shown in FIG. 37 may include ahomogenous mixture of containers or may be deployed with a diverseheterogeneous mixture of different types of containers that are eachnode-enabled and operative to communicate with facility master node37110 a through their respective container nodes. And while furtherdetails of a particular exemplary container appears in FIG. 38 andfurther details of the node-based element disposed relative to thatcontainer appears in FIG. 39, the principles of such an embodiment of acontainer node element as disposed and used relative to the particularcontainer may apply to each of containers C and D in their furtherhierarchy and nested relationship.

As shown in FIG. 37, the container node elements respectively disposedas part of containers A-D may separately communicate internally withnode-enabled packages (or other node-enabled containers) respectivelymaintained therein while also being able to communicate with facilitymaster node 37110 a. In this way, the container node element may operateas a node similar to a master node but that needs not know its location,and as such it can provide a further level within the hierarchy to helpmanage as well as allow for robust and improved ways of to communicatewith the facility master node 37110 a.

FIG. 38 provides further details on an embodiment of system 3700. Inparticular, FIG. 38 is a diagram illustrating an embodiment of exemplaryenhanced logistics system 3700 for managing a multi-level wireless nodenetwork with further details regarding exemplary container 37100A and arelated exemplary container node 38000 shown with node-enabled packages38100A-D maintained within the container 37100A in accordance with anembodiment of the invention. Referring now to FIG. 38, container node38000 is shown as an additional and intermediate node that helps tooffload some of the node management responsibility normally incumbentupon facility master node 37110. Container 37100A is shown as at leasttemporarily maintaining packages 38100A-38100D within an interior of thecontainer 37100A. And as shown in FIG. 38, each of packages38100A-38100D is a node-enabled package that has a respectively relatedone of ID nodes 38120A-38120D. In this manner, deployment of an ID node(such as nodes 38120A-38120D) within a package (such as packages38100A-38100D) allows for monitoring and managing of the package via therelated ID node as managed by container node 38000. While the relevantID node is shown in FIG. 38 as being disposed within an interior of thepackage, those skilled in the art will appreciate that principles ofthese container node related embodiments are also applicable if thepackage ID node is implemented as an ID node incorporated into thepackaging material itself or an ID node simply attached to an item beingshipped. Thus, for purposes of these container node related embodiments,an exemplary package ID node may be implemented with an ID node placedwithin a package being shipped, with an ID node attached to the package,with an ID node incorporated into the packaging material of the package(or its internal cushioning material), or with an ID node simplyattached to the item being shipped without further physical packagingmaterial.

As shown in FIG. 38, exemplary container node 38000 is typicallydeployed as a container-centric intermediary node within the multi-levelwireless node network system 3700. Embodiments of exemplary containernode 38000 may be disposed in a various physical configurations relativeto container 37100A. In general, container node 38000 may be disposedand considered part of container 37100A. For example, one embodiment ofcontainer node 38000 may be integrated or incorporated into thestructure of container 37100A (e.g., built into the structure ofcontainer 37100A, such as the ceiling, walls, floor, or doors thatprovide ingress and egress). Another embodiment of container node 38000may still be part of the container but be simply attached to thecontainer (e.g., attached to a surface within the interior of container37100A or attached to a surface on the exterior of container 37100A).

Further embodiments of exemplary container node 38000 may includecertain components (e.g., sensors, antennas in communication with IDnodes A-D 38120A-D, etc.) exposed to the internal of the container37100A while other components (e.g., sensors, antennas in communicationwith facility master node 37110 a) may be exposed to the exterior of thecontainer 37100A to enhance connectivity to internal node elements aswell as external node elements. As will be explained in more detailbelow, enhanced system scanning capabilities may leverage off using thistype of exemplary container node 38000 in addition to fixed facilitymaster nodes (such as node 37110 a), along with localized scanning andmore intelligent & efficient use of the expanded hierarchy of nodes inthe network to accomplish scanning for package ID nodes in order tobetter handle congestion issues with large volumes of packages andpackage ID nodes being handled in a given facility.

FIG. 39 provides even more detail about components making up anexemplary container node 38000 as an apparatus. In particular, FIG. 39is a diagram illustrating further details of the exemplary containernode 38000 deployed within a multi-level wireless node network 3700 asshown in FIG. 38 where the network operating environment for thecontainer node includes a package ID node associated with a package, afacility master node associated with a facility, and a server inaccordance with an embodiment of the invention. Referring now to FIG.39, those skilled in the art will appreciate that one embodiment ofexemplary container node 38000 includes many of the same hardware, code,and data components as shown for exemplary master node 110 a of FIG. 4,but simplified so as not to include location circuitry. As such, similarfunctionality exists for what is numbered the same and described aboveregarding exemplary master node 110 a of FIG. 4. Thus, while master node110 a shown in FIG. 4 includes processing unit 400, memory storage 415,volatile memory 420, clock/timer 460, sensors 465, battery/powerinterface 470, short range communication interface 475, and medium/longrange communication interface 480, exemplary container node 38000 mayuse similar hardware components as shown in FIG. 39 including processingunit 38400, memory storage 38415, volatile memory 38420, clock/timer38460, sensors 38465, battery/power interface 38470, short rangecommunication interface 38475, and medium/long range communicationinterface 38480.

Notably, one embodiment of exemplary container node 38000 illustrated inFIG. 39 deploys container control and management code 38425 (as storedin memory storage 38415 and loaded for execution by processing unit38400 in volatile memory 38420), which is similar in functionality tomaster node control and management code 425 described above in moredetail. Essentially, container control and management code 38425operates similar to that as described above for master node control andmanagement code 425 but further includes program code for enhancedmanagement of package ID nodes and interactions with facility masternode as described in more detail below with respect to FIG. 40. Thus, inthe illustrated embodiment, such further program code is implemented asan integrated part of container control and management code 38425, suchas one or more programmatic functions or additional program moduleswithin code 38425. But in other embodiments, the further program codeused to implement the method as described with respect to FIG. 40 may beimplemented separately from code 325.

Those skilled in the art will also appreciate that another embodiment ofa container node (not shown) may be implemented similar to an ID node,such as ID node 120 a as shown and explained relative to FIG. 3, butwith the addition of a medium/long range communication interface and useof further program code as part of or in conjunction with node controland management code 325 for enhanced management of package ID nodes wheninteracting with the package ID nodes and a facility master node asdescribed in more detail below with respect to FIG. 40. Thus, this othertype of embodiment of an exemplary container node would still have nolocation circuitry (as ID node 120 a does not typically include suchcircuitry) but would be able to communicate over the two differentcommunication interfaces for short range communication (e.g., BLE typeof low power and short range formatted communications) and longer rangecommunication (e.g., higher power and longer range cellular or Wi-Fiformatted communications). According, those skilled in the art willappreciate that an embodiment of a container node based upon suchmodifications to a ID node platform essentially works similarly to amaster node that either does not know its own fixed location or does nothave the ability to self-determine its own location though its owncomponents.

An embodiment of the exemplary control and management code 38425 thatprovides for enhanced management of package ID nodes via interactionswith package ID nodes and a facility master node as described in moredetail below with respect to FIG. 40 may also include rules for managingwhich of its two different communication interfaces to use whencommunicating with the facility master node. In some embodiments,container node 38000 may have node processing unit communicating withfacility master node 37110 a over the medium/long range communicationinterface 38485 because the distance between the facility master node37110 a and container node 38000 may be too far for effectivecommunications using the short range communication interface 38480. Assuch, range between the nodes may be a factor considered by theprocessing unit 38400 within container node 38000 when determining howto accomplish communicating with the facility master node 37110 a.

However, when the range between the container node 38000 and facilitymaster node 37110 a is close enough to where the container node 38000either interface may be used to established communications with thefacility master node 37110 a, other factors may be considered whendetermining which interface on the container node to use, such asrelative congestion of data communications on the short range modes ofcommunication versus the longer range mode of communication.

In another embodiment, container node 38000 may depend upon themedium/long range communication interface 38480 when node-to-nodecommunications may not be possible with the short range communicationinterface 38485. For example, a ULD having a container node may beloaded on an aircraft where the vehicle master node or facility masternode may not have an operating short range communication interface (orbe implemented with a facility master node at a level in the networkbetween the container node and a server, but where the facility masternode implemented in this situation is not equipped with a short rangecommunication interface). As such, container node 38000 is operative todetermine which of the communication interfaces to use, and broadcastmessages to and received messages from the facility master node using anappropriate one of the two communication interfaces onboard thecontainer node 38000.

In operation, such an exemplary container node 38000 may function in aparticularly programmed and collectively unconventional manner to add afurther management layer within an exemplary wireless node network. FIG.40 explains an embodiment of this further with a flow diagramillustrating an exemplary method for managing a multi-level wirelessnode network having a plurality of package ID nodes at a first level ofthe network, a container node at a second level of the network, afacility master node at a third level of the network, and a server atfourth level of the network in accordance with an embodiment of theinvention. Referring now to FIG. 40, method 4000 begins at step 4005with a container node detecting an advertising signal broadcast by eachof the package ID nodes where the container node is part of a logisticscontainer and each of the package ID nodes are respectively associatedwith one of a plurality of packages. For example, exemplary containernode 38000 may perform step 4005 as shown in FIG. 38 by detectingadvertising signals from each of ID nodes A-D 38120A-38120D, which arerespectively associated with each of packages 38100A-38100D withincontainer 37100A (which may be temporarily maintained within a mobile orstatic facility associated with facility master node 37110 a). Thus,exemplary container node 38000 may perform step 4005 as a way ofdedicated but generally localized scanning specific to the container.

At step 4010, method 4000 continues with the container node detecting anadvertising signal broadcast by the facility master node as thecontainer node approaches a facility associated with the facility masternode. As such, an embodiment of method 4000 may have the container nodeat step 4010 detecting an advertising signal broadcast by the facilitymaster node prior to when the container node arrives or is received atthe facility associated with the facility master node. Thisadvantageously allows for and facilitates enhanced management operationsrelated to the packages being shipped within the container prior toarrival and reception at the facility.

At step 4015, method 4000 continues with the container node offloadingmanagement control of each of the package ID nodes from the facilitymaster node to the container node as part of managing the first level ofthe network. In a more detail embodiment, offloading management controlof each of the package ID nodes may involve distributing scanningresponsibility for the package ID nodes from the facility master node tothe container node so that the facility master node is not burdened withsuch scanning responsibility on the first level of the network.

Further still, the management control offloaded to the container node aspart of step 4015 may involve various control and managerial tasks to beperformed by the container node. For example, the management controloffloaded may be controlling a broadcast setting for at least one of thepackage ID nodes. In particular, such control of the broadcast settingmay have the container node identifying a location for the one of thepackage ID nodes in response to a location request received from theserver by the facility master node. In this way, the container node(rather than the facility master node) may interact with one or more ofthe package ID nodes to determine the location of one of the package IDnodes and free up the facility master node to handle other higher leveltasks.

Further still, an embodiment where the container node offloadsmanagement control of each of the package ID nodes from the facilitymaster node as part of step 4015 may be implemented in various degreesand, in some cases, depend upon a threshold level of node congestionwithin a part of the wireless node network normally serviced by thefacility master node. For example, if there are less than 10 containerswithin the facility serviced by the facility master node 3711, thecontainer node 38000 may operate by taking on responsibility for asmaller subset of the tasks normally assigned to the facility masternode when monitoring and communicating with package ID nodes (e.g.,monitoring status, changing broadcast settings, gathering sensor data,determining relative location information, etc.). Likewise, if there are10 or more, an embodiment of a container node may operate to offload alarger subset of the overall management control related to the packageID nodes from the facility master node so that the facility master nodeis less burdened from the relatively large number of containers servicedand monitored.

In a further detailed embodiment, offloading management control may havethe container node communicating with each of the package ID nodes aspart of monitoring and controlling the package ID nodes, receivingresponses from the package ID nodes, and determining relevant nodeinformation (such as status information about at least one of thepackage ID nodes) from the responses received.

At step 4020, method 4000 has the container node transmitting relevantnode information to the facility master node, where the relevant nodeinformation provides information about at least one of the packages inthe logistics container and where the provided information reflectsstatus information to be sent to the server by the facility master node.In this manner, the container node may transmits the result of one ormore of the offloaded management control tasks so that the facilitymaster node may make use of such information without the typicallyincumbent management interaction and control of those nodes at the firstlevel of the network. In a more detailed embodiment, transmitting therelevant node information may further involve formatting a message fortransmission using a long range communication interface on the containernode (such as communication interface 38485) where the message providesthe relevant node information as an update for the server, and thensending the message to the facility master node using the long rangecommunication interface on the container node.

Step 4020 may also be implemented in some embodiments with thetransmitted relevant node information providing at least someinformation on the one of the package ID nodes to be to be forwarded tothe server as package ID node update information by the facility masternode without requiring the facility master node to directly interactwith any of the package ID nodes. The relevant node information in someembodiments may provide information (e.g., one or more of location data,profile data, security data, association data, shared data, and sensordata) about one of the package ID nodes associated with the one of thepackages in the logistics container. Such sensor data may be provided asrelevant node information, for example, and be or include data collectedfrom a sensor on one of the package ID nodes or, in more detail, wherethe sensor data relates to at least one condition of the one of thepackages as detected by the sensor (such as sensors 38465). Suchlocation data may be provided as relevant node information, for example,and be or include data identifying a location for the one of the packageID nodes in response to a location request passed to the container nodefrom the facility master node.

Further embodiments of method 4000 may provide more detail regardingvarious steps by leveraging multiple communication interfaces on thecontainer node. For example, in one further embodiment, the containernode may adaptively detect the advertising signal broadcast by thefacility master node and transmit the relevant node information to thefacility master node using one of a plurality of communicationinterfaces on the container node depending on communication congestionwithin a part of the wireless node network normally serviced by thefacility master node. Thus, which of the communication interfaces may beused by the container node communicating with the facility master nodeper method 4000 may be done adaptively based on node congestion levels.If the short range communication path is crowded because, for example,the container maintains a large number of broadcasting package ID nodesor there are an unusually large number of containers that collectivelymaintain such a large number of broadcasting package ID nodes that mustcommunicate over the short range communication path, the container nodemay adaptively select the medium/long range communication interface anduse that for communicating with the facility master node. Likewise, ifthe short range communication path is relatively clear (e.g., there areonly a small number of package ID nodes that may or may not bebroadcasting over the short range communication path), the containernode may adaptively select the short range communication interface anduse that for communicating with the facility master node. Use of theshort range versus the long range communication interface may also beaccording to a profile of rules maintained as part of profile data 430on container node 38000 where such rules define different situationswhere one communication interface is preferred over the other. Such aprofile of rules may be deployed when selectively or adaptivelydetecting or transmitting as explained above.

In somewhat similar fashion, in another embodiment, the container nodemay adaptively detect the advertising signal broadcast by the facilitymaster node and transmit the relevant node information to the facilitymaster node using one of the multiple communication interfaces on thecontainer node depending on the ability of the facility master node tohandle communications formatted for the one of the plurality ofcommunication interfaces. For example, facility master node 37110 a maybe disposed at a location or position that is too far and out of rangefor the short range communication interface 38480 on container node38000. Thus, facility master node 37110 a may not be in a position tohandle communications from container node 38000 formatted for the shortrange communication interface 38480 (e.g., BLE formatted communications)but may still be able to hand communications formatted for themedium/long range communication interface 38485 (e.g., Wi-Fi or cellularformatted communications).

In still further embodiments of method 4000, localized scanning may bemore specifically implemented as part of step 4005. For example, in oneembodiment, the container node may detect the advertising signalbroadcast by each of the package ID nodes by localized scanning for eachof the package ID nodes proximate to the logistics container using ashort range communication interface on the container node (such as shortrange communication interface 38480 that can communicate over a specificshort-range communication path using various types of short-rangecommunication protocols (e.g., a Bluetooth® Low Energy (BLE) protocols,NFC protocols, ultra-wideband impulse radio communication protocols,ZigBee protocols, IEEE 802.15.4 standard communication protocols, andthe like). In more detail. localized scanning may be implemented withthe communication interface listening for the advertising signalbroadcast from within the logistics container or proximate to anexterior of the logistics container.

Method 4000 as explained above focuses on the unconventional andadvantageous operation of a container node that helps offload managementcontrol from the facility master node. Further embodiments of method4000 may be implemented when the container node is used with differentkinds of logistics container. For example, the logistics container asused in method 4000 may include, but is not limited to a unit loaddevice (ULD) container capable of being transported within an airplane;a trailer capable of being moved by a truck; a train car capable ofbeing moved on a railway system; or an intermodal shipping containercapable of being moved on at least two different types of transportationmodalities.

Those skilled in the art will appreciate that method 4000 as disclosedand explained above in various embodiments may be implemented on acontainer node (e.g., container node 38000 attached to a logisticscontainer 37100A used to temporarily maintain items or packages38100A-38100D) running one or more parts of container node control andmanagement code (e.g., code 38425). Such code may be stored on anon-transitory computer-readable medium, such as memory storage 38415 oncontainer node 38000. Thus, when executing code 38425, the containernode's processing unit may be programmatically transformed to becomeunconventionally operative to perform operations or steps from theexemplary methods disclosed above, including method 4000 and variationsof that method.

In more detail, an exemplary container node apparatus may be deployedwithin a multi-level wireless node network to help manage part of thenetwork, which has at least a package ID node associated with a package,a facility master node associated with a facility, and a server (such asthat shown in FIGS. 38 and 39). The container node in this detailedapparatus embodiment includes a node processing unit, a memory storage,and two different communication interfaces. The node processing unit isdisposed as at least part of a logistics container—e.g., built as anintegrated part of the logistics container, included part of a containernode module to which the processing unit is attached or otherwiseaffixed and disposed relative to the logistics container, and the like.For example, an exemplary module having the container node's processingunit may be disposed as a part of the logistics container in a removableconfiguration so that the module may be temporarily secured to thelogistics container and removed for service or use in another logisticscontainer.

The memory storage and each communication interface are respectivelycoupled to the node processing unit of the container node. The memorystorage is operative non-transitory memory that at least maintainscontainer node management code for execution by the node processing unit(such as container control and management code 38425 as described inmore detail above relative to FIGS. 39 and 40). The first communicationinterface coupled to the node processing unit operates to communicatewith the package ID node over a first communication path in accordancewith the container node management code. The second communicationinterface coupled to the node processing unit operates to communicatewith the facility master node over a second communication path inaccordance with the container node management code. In this manner,consistent with the exemplary container node 38000 as shown in FIG. 38,the container node apparatus is disposed at a level in the multi-levelwireless node network between the package ID node and the facilitymaster node.

The node processing unit of the container node operates to execute thecontainer node management code, which then causes the container nodeapparatus to become specially programmed to help manage and control partof the multi-level wireless node network as the container node performthe steps and operations as described above relative to method 4000 andvariations of that method described above that collectively transformthe container node apparatus in a non-conventional and innovativemanner. More specifically, an embodiment may have the node processingunit of the container node apparatus being operative, when running thecontainer node management code, to specially adapt the container nodeapparatus to become operative to detect, via the first communicationinterface, an advertising signal broadcast by the package ID node;detect, via the second communication interface, an advertising signalbroadcast by the facility master node as the logistics containerapproaches the facility associated with the facility master node;control, via the first communication interface, the package ID node aspart of managing the first level of the network and without directcommunications between the package ID node and the facility master nodeto offload management responsibility for the package ID node from thefacility master node; and cause the second communication interface totransmit relevant node information by the container node to the facilitymaster node, where the relevant node information provides informationabout the package and reflects status information to be forwarded as anupdate to the server by the facility master node (which may beimplemented as a mobile master node associated with a mobile facilitycapable of temporarily maintaining the logistics container).

Further embodiments of such a container node may interact with thepackage ID node through the first communication interface to offloadmanagement responsibility for the package ID node from the facilitymaster node in various ways that delegate managing this first level ofthe network. For example, the node processing unit may be operative tocontrol, via the first communication interface, the package ID node bybeing further operative to (a) communicate with the package ID node aspart of monitoring and controlling the package ID node at least as thelogistics container approaches the facility (e.g., prior to arrival atthe facility or receipt at the facility) or as the logistics containerremains within the facility; (b) receive, through the firstcommunication interface, a message from the package ID node; and (c)determine relevant node information from the response. This relevantnode information would include at least status information about thepackage ID node and provides at least some information on the package IDnode to be forwarded to the server as package ID node update informationby the facility master node without requiring the facility master nodeto directly interact with the package ID node.

In another example of offloading management responsibility, the nodeprocessing unit may be able use the first communication interface tocontrol the package ID node by being further operative to send thepackage ID node a control message through the first communicationinterface, where the control message adjusts a broadcast setting for thepackage ID node. In this situation, the control message may be part ofidentifying a location of the package ID node in response to a locationrequest received from the server by the facility master node andforwarded to the node processing unit over the second communicationinterface.

In yet another embodiment with further details on offloading managementresponsibility, the node processing unit may use the first communicationinterface to control the package ID node (instead of having the facilitymaster node responsible for controlling the package ID node directly)based upon a threshold level of node congestion within a part of thewireless node network normally serviced by the facility master node.

In still further embodiments of the container node apparatus, differenttypes of relevant node information may transmitted by the container nodeto the facility master node. For example, an embodiment may have therelevant node information providing information about the package IDnode via at least one of location data, profile data, security data,association data, shared data, and sensor data. Such sensor data mayinclude data collected from a sensor on the package ID node (wherein thesensor data relates to at least one condition of the package).Additionally, such location data may identify a location for the packageID node in response to a location request passed to the container nodefrom the facility master node. Thus, various types of data may be usedin embodiments as the relevant node information to be transmitted to thefacility master node.

In some embodiments, detecting signals from the package ID node may beimplemented with localized scanning. In particular, the node processingunit may be operative to use the first communication interface to detectthe advertising signal broadcast by the package ID node by causing thefirst communication interface to conduct localized scanning proximate tothe logistics container, and cause the second communication interface totransmit a message with the relevant node information gathered from thelocalized scanning. In more detail, such localized scanning proximate tothe logistics container may have the node processing unit being furtheroperative to command the first communication interface to listen for theadvertising signal broadcast from the package ID node located within thelogistics container or located proximate to an exterior of the logisticscontainer. In such a way, the node processing unit of the container nodemay help manage the first level of the network by being responsible forscanning for the package ID node instead of having the facility masternode scanning for the package ID node.

Further embodiments of the container node apparatus may be used withdifferent kinds of logistics containers. For example, the logisticscontainer may include, but is not limited to a unit load device (ULD)container capable of being transported within an airplane; a trailercapable of being moved by a truck; a train car capable of being moved ona railway system; or an intermodal shipping container capable of beingmoved on at least two different types of transportation modalities.

Additional embodiments of the container node apparatus may deploy rulesfor the node processing unit on what interface to use when communicatingwith the facility master node. For example, the node processing unit maybe operative to detect the advertising signal broadcast by the facilitymaster node by communicating with the facility master node over one ofthe first communication path and the second communication path dependingon communication congestion within a part of the wireless node networknormally serviced by the facility master node or depending on theability of the facility master node to handle communications formattedfor the one of the plurality of communication interfaces. The existingcongestion level relative to particular communication paths may begauged in order for the container node to apply such communication ruleson how it may effectively communicate with the facility master node.Likewise, rules on communication ranges or confirmed communication linksfor particular paths may be used when applying such rules and using anappropriate communication interface on the container node to communicatewith the facility master node.

In light of the above discussion relative to an exemplary container nodeapparatus (as shown in FIGS. 38 and 39) and methods where such anexemplary container node may be deployed to interact with a multi-levelnetwork to help manage at least part of the network (as explained viathe flowchart shown in FIG. 40), a further system embodiment may bedescribed with reference to FIGS. 38-40. In particular, an exemplaryenhanced logistics system for managing a multi-level wireless nodenetwork involving a plurality of packages may be described as follows.The exemplary system embodiment may include a server, a facility masternode, a container node, and a plurality of package ID nodes respectivelyassociated one of the packages. The server is disposed at a top level ofthe multi-level wireless node network and maintains information onadditional node elements of the multi-level wireless node network. Thefacility master node, which is associated with a facility that cantemporarily maintain the packages, is disposed at a second level of themulti-level wireless node network and deployed in operativecommunication with the server. The container node is disposed at a thirdlevel of the multi-level wireless node network and is deployed as partof a logistics container that currently maintains the plurality ofpackages (such as an integral, fixed, or removable part of the logisticscontainer). The container node includes a long range communicationinterface providing access to a long range communication path and ashort range communication interface providing access to a short rangecommunication path distinct from the long range communication path. Assuch, the container node is in operative communication with at least thefacility master node over the long range communication path using thelong range communication interface. The package ID nodes are disposed ata fourth level of the multi-level wireless node network where each ofthe package ID nodes are respectively associated with one of theplurality of packages currently maintained with the logistics containeras mentioned above. Each of the package ID nodes is in operativecommunication with the container node over the short range communicationpath via the short range communication interface of the container node.

As part of this exemplary enhanced systems embodiment, as the containernode enters the facility associated with the facility master node (suchas prior to when the container node has arrived or been received at thefacility), the container node may operate to offload managementresponsibility for each of the package ID nodes from the facility masternode when the container node uses the short range communicationinterface to control each of the package ID nodes without directcommunication between the package ID node and the facility master node.In this way, the facility master node is not responsible for directlycommunicating with each of the package ID nodes. Further, the containernode may also operate in the same situation to use the long rangecommunication interface to transmit relevant node information to thefacility master node. Such relevant node information is generallyinformation about at least one of the packages that is gathered by thecontainer node from at least one of the package ID nodes. Such relevantnode information also reflects status information on at least one of thepackages to be forwarded as an update by the facility master node to theserver.

Controlling a package ID node is a way the system's container node mayoffload management responsibility from the facility master node. Thecontainer node may use the short range communication interface tocontrol each of the package ID nodes by being further operative to sendeach of the package ID nodes a control message through the short rangecommunication interface (e.g., via a BLE formatted short range wirelessmessage), where the control message adjusts a broadcast setting for therespective package ID node. For example, the control message may be partof identifying a location of at least one of the package ID nodes inresponse to a location request received from the server by the facilitymaster node and forwarded to the container node over the long rangecommunication interface. As such, the control message from the containernode may instruct the respective package ID node to vary its broadcastoutput power level as part of a locating technique deployed to locatethe package ID node.

Further system embodiments may have the relevant node informationproviding information about the one of the package ID nodes, and furtherinclude at least one of location data, profile data, security data,association data, shared data, and sensor data related to the particularpackage ID node. Such sensor data may, for example, include datacollected from a sensor on the one of the package ID nodes (where thesensor data may relate to at least one condition of the one of thepackages—e.g., temperature, light, humidity/moisture, pressure,impact/shock, and the like related to an environment conditionexperienced by the particular package). And such location data, forexample, may identify a location for the one of the package ID nodes inresponse to a location request passed to the container node from thefacility master node.

The system's container node may also, in some embodiments, offloadmanagement responsibility for the package ID nodes from the facilitymaster node when at least a threshold level of node communicationcongestion exists within a part of the wireless node network normallymanaged directly by the facility master node. For example, the containernode may measure a level of node communication activity via one or bothof its communication interfaces to establish a level of nodecommunication congestion experienced by the facility master node. If themeasured level exceeds a threshold level, the container node may beactivated to further offload management and interactive tasks relatingto the package ID nodes maintained within the container node's logisticscontainer.

Further still, the system's container node may, in some embodiments,offload management responsibility by conducting localized scanning viathe short range communication interface proximate to the logisticscontainer to detect an advertising signal broadcast by each of thepackage ID nodes. In a further embodiment, the container node mayconduct localized scanning via the short range communication interfaceproximate to the logistics container by using the short rangecommunication interface to listen for the advertising signal broadcastfrom each of the package ID nodes located within the logistics containeror located proximate to an exterior of the logistics container (e.g., asthe logistics container is being loaded or unloaded and the package withthe package ID node is not yet inside the container or has been unloadedto just outside the container). Thus, the system's container node maydeploy its short range communication interface to accomplish interactingand interfacing with package ID nodes rather than have the facilitymaster node be directly responsible for them. Stated another way, thesystem's container node may be responsible for using its short rangecommunication interface to scan for each of the package ID nodes as partof managing the fourth level of the multi-level wireless node networkwhile avoiding the overloading the facility master node with congestedscanning responsibilities related to the plurality of package ID nodesand additional node devices in the wireless node network.

As with the container node embodiments and method embodiments describedabove, the container node in the exemplary enhanced system embodimentmay be used with different kinds of logistics containers. For example,the logistics container may include, but is not limited to a unit loaddevice (ULD) container capable of being transported within an airplane;a trailer capable of being moved by a truck; a train car capable ofbeing moved on a railway system; or an intermodal shipping containercapable of being moved on at least two different types of transportationmodalities. Those skilled in the art will appreciate that use of theterm “container” need not be a simple box-like structure, but itself mayinclude a defined holding area on a transport or conveyance responsiblefor shipping items within the holding area (e.g., packaged items thathave a package ID node that may be scanned by a container node attachedto the transport or conveyance in or near the relevant holding area).

Additionally, the facility master node involved in this systemembodiment may be associated with a mobile facility (as opposed to afixed or stationary facility) that is capable of temporarily maintainingthe logistics container. Example of such a mobile facility may be anairborne cargo hold capable of temporarily maintaining multiple ULDcontainers and having a mobile master node (such as airborne mobilemaster node 9415 shown in FIG. 21).

Those skilled in the art will appreciate that, in light of the detailsdescribed above, other system embodiments may be deployed with fewerelements than described above. For example, a broader system embodimentmay include the container node as described above along with a facilitymaster node. The container node and facility master node in such anembodiment may operate and interoperate as described above, but thesystem embodiment need not necessarily include the package ID nodesbeing scanned or the server. Still another system embodiment may includethe facility master node, container node, and at least one package IDnode as described above without the explicit inclusion of a server atthe top level of the network as an additionally required element of theparticular system embodiment. Likewise, yet another system embodimentmay include a server, facility master node, and container node asexplicitly recited elements and as described above as operating andinteroperating. Thus, the package ID nodes may not be expressly includedas elements in this system embodiment, but the recited container node inthe system would still operate to help manage those components on thelower level of the network.

Proactive Movement Notification Using Detectors on a Container Node

As explained above relative to FIGS. 38 and 39, a container node may bedeployed with a logistics container at one level of a wireless nodenetwork and used to help manage at least a portion of the network.However, a further embodiment of a container node may be deployed withparticular hardware and software components used to sense movementsrelative to the container and respond to such detected movement invarious ways as part of the wireless node network. For example, thistype of aspect may have an exemplary container node using anaccelerometer or other type of movement or motion sensor (e.g., aninertial type of device) to detect movement and respond by notifyingother network elements (e.g., package ID nodes, facility master nodes,server, and the like) regarding such movement or altering a broadcastprofile based on the movement. In such an example, if the container issensed as staying put or coming to rest, relevant nodes associated withthe container may not need to broadcast frequently or may go into a“sleep” mode until movement is detected and only then start broadcastingagain.

FIG. 41 is a diagram illustrating an exemplary motion sensing containernode in accordance with an embodiment of the invention. Referring now toFIG. 41, exemplary motion sensing container node 41000 is shown similarto container node 38000 (which was earlier described as being similar insome embodiments to a master node of FIG. 4 without location circuitry).More specifically, those skilled in the art will appreciate that oneembodiment of exemplary container node 41000 includes many of the samehardware, code, and data components as shown for exemplary master node110 a of FIG. 4, but simplified so as not to include location circuitry,as well as to that of exemplary container node 38000 illustrated in FIG.39. As such, similar functionality exists for what is numbered the sameor similarly and described above regarding exemplary master node 110 aand exemplary container node 38000. Thus, while master node 110 a shownin FIG. 4 is described as having processing unit 400, memory storage415, volatile memory 420, clock/timer 460, sensors 465, battery/powerinterface 470, short range communication interface 475, and medium/longrange communication interface 480, exemplary container node 38000 mayuse similar hardware components as shown in FIG. 39. This includesprocessing unit 38400, memory storage 38415, volatile memory 38420,clock/timer 38460, sensors 38465, battery/power interface 38470, shortrange communication interface 38475, and medium/long range communicationinterface 38480. Likewise, exemplary motion sensing container node 41000may use similar use similar hardware components as shown in FIG. 41including processing unit 41400, memory storage 41415, volatile memory41420, clock/timer 41460, battery/power interface 41470, short rangecommunication interface 38475, and medium/long range communicationinterface 41480.

Further, the embodiment of exemplary container node 41000 illustrated inFIG. 41 deploys container control and management code 41425 (as storedin memory storage 41415 and loaded for execution by processing unit41400 in volatile memory 41420), which is similar in functionality tocontainer control and management code 38425 as well as master nodecontrol and management code 425 described above in more detail. Suchcode, as previously described, generally controls the behavior of thenode relating to communications (with a node advertise and query logicmanager), information management (with an information control andexchange manager), power management (with a node power manager thatinteracts with the various communication interfaces, for example, tomanage power consumption and broadcast power aspects at a low level),and association management (with an association manager). As such,container control and management code 41425 essentially operates similarto that as described above for container node control and managementcode 38425 (and master node control management code 425 but without theneed for a location aware/capture module) but further includesmotion-based management program code 41500 for motion-based managementof a logistics container as described in more detail below with respectto the method described relative to FIG. 43. Thus, an embodiment ofmotion-based management program code 41500 may be implemented as anintegrated part of container control and management code 41425, such asone or more programmatic functions or additional program modules thatmay be called within code 41425. However, in other embodiments, themotion-based management program code 41500 used to implement the methodas described with respect to FIG. 43 may be implemented separately fromcode 41425 in a way that allows code 41500 to call some of theprogrammatic functions or program modules described as part of code 425to implement the steps as laid out in the method of FIG. 43 andvariations of that method as described herein.

In general, exemplary motion-based management code 41500 adaptscontainer node 41000 such that the node detects motion-based events andresponds in a way that intelligently alters a broadcast profile that isbeing currently used by the container node 41000. An exemplary broadcastprofile may include a collection of one or more operating parametersused by the container node 41000 when broadcasting over one of thecommunication interfaces 41480, 41485. Such operating parameters, forexample, may include parameters related to a broadcast output powerlevel to use when communicating with other nodes or the frequency withwhich the relevant communication interface broadcasts (or whether it isto remain silent for a set duration). In some embodiments, a singlebroadcast profile for node 41000 may be maintained as part of profiledata 460. In other embodiments, such as that shown in FIG. 41, containernode 41000 maintains multiple broadcast profiles 41330 resident inprofile data 460 of memories 41420/41415. Typically, motion-basedmanagement code 41500 determines which communication profile to use(e.g., indoor broadcast profile, congested landscape broadcast profile,an outdoor broadcast profile, an airborne broadcast profile, and thelike), and the selected communication profile from broadcast profiles41330 may then be altered accordingly in response to motion-based eventsas described in more detail below. Those skilled in the art willappreciate that the availability of multiple different broadcastprofiles to use allows for a proactive selection of a desiredcommunication profile to fit with a particular type of node operatingenvironment.

As a measuring front end component for such motion-based managementinvolving a logistics container, exemplary motion sensing container node41000 includes various sensors, such as motion sensor 41465 as a sensoror detector with one or more sensing elements that can collectivelydetect a motion status relative to that which it is attached (e.g., alogistics container or part thereof). An exemplary implementation ofmotion sensor 41465 (or other sensors 41467) may include additionalhardware (e.g., local sensor memory, battery backup, multiplexinghardware interfaces when using multiple sensing elements) and/orprogram/firmware features to manage the collection, storage, and sharingof the captured motion-related sensor data (such as motion statusinformation). In some embodiments, motion sensor 41465 may beimplemented with several types of motion sensors or motion/movementdetectors, such as an inertial sensor, a shock detector, anaccelerometer, a microelectromechanical (MEMS) sensor, and the like. Andwhile sensor 41465 is explicitly shown in FIG. 41 as a motion sensor,those skilled in the art will appreciate that an embodiment of containernode 41000 may also include other types of sensors or detectors 41467,such as one or more magnetic sensors (e.g., a magnetometer, gyroscopicsensor, etc.), electronic sensors (e.g., a voltage sensor, currentsensor, electronic power sensor, etc.), and environmental sensors (e.g.,pressure, light, temperature, humidity, magnetic field, altitude,attitude, orientation, proximity, etc.).

Exemplary container node 41000 as shown in FIG. 41 may be deployed aloneor as part of various system embodiments providing node-implementedmotion-based management of a logistics container, such as that shown inFIG. 42. In particular, FIG. 42 is a diagram illustrating an exemplarymotion-based management system 4200 for an exemplary logistics container37110A that uses an exemplary motion sensing container node 41000 inaccordance with an embodiment of the invention. Referring now to FIG.42, container node 41000 is shown attached to logistics container37100A.

In general, the illustrated embodiment of logistics container 37100A isa box-like container made with a structural housing 37200 surroundingand defining an interior storage area within the housing 37200 capableof maintaining multiple items and/or packages. The container's door37205 generally secures the interior storage area when in a closedposition relative to the housing 37200 and provides access to theinterior storage area through an opening or entrance when in an openposition relative to the housing 37200. In the illustrated embodiment ofFIG. 42, door 37205 is movably coupled to the housing portion via a setof one or more hinges as part of the door 37205 and attached to thehousing 37200. Other embodiments of container 37100A may have differenttypes of doors or other movable panels that may be configured to securethe interior storage area of a container.

The exemplary motion-sensing container node 41000 shown in FIG. 42 (andshown in greater detail in FIG. 41) is disposed as part of system 4200and has an exterior housing 41600 that contains and protects theelectronic hardware and components of the node 41000 (such as thoseshown in FIG. 41). As such, the housing 41600 of motion-sensingcontainer node 41000 may be fixed or removably held in an attachedposition relative to the logistics container 31700A. In more detail, anembodiment the housing 41600 of motion-sensing container node 41000 maybe disposed entirely within the housing 37200 of container 31700A, whileanother embodiment may have the housing 41600 of motion-sensingcontainer node 41000 attached to the logistics container in such amanner where a portion of the housing 41600 for node 41000 is exposed tothe interior storage area defined within housing 37200 of container37100A while another portion of housing 41600 is exposed outside of thecontainer 37100A. For example, an embodiment of node 41000 may use a41600 housing that allows for one or more antennas of the node 41000 tobe exposed outside of the container 37100A while allowing for one ormore sensors (such as motion sensing elements 41465 a-41465 c thatcollectively implement an exemplary motion sensor 41465 as shown in FIG.41) of the node 41000 to be exposed and deployed within the interiorstorage area of the container 37100A.

Within housing 41600, the exemplary motion-sensing container node 41000includes at least a node processing unit (such as unit 41400) and amemory storage (such as memory storage 41415 and/or volatile memory41420). The memory storage and the node processing unit are typicallydisposed within the housing 41600. The memory storage is coupled to thenode processing unit and maintains at least motion-based management code(such as motion based management code 41500) for execution by the nodeprocessing unit 41400 and a broadcast profile (such as at least one ofbroadcast profiles 41330) defining at least one operationalcommunication parameter for the container node 41000. The container node41000 further includes at least a communication interface coupled to thenode processing unit 41400 and operative to communicate with a secondnode over a communication path in accordance with the broadcast profilemaintained in the memory storage. Those skilled in the art willappreciate that the communication interface may include transceiverhardware and firmware suitable for transmitting and receiving relevantmessages in a format and paradigm corresponding to the communicationpath used to communicate with the second node.

As noted above, node 41000 further includes a motion sensor coupled tothe node processing unit, where the motion sensor operates to detect amotion status of the logistics container and report the detected motionstatus to the node processing unit. Such a motion status may include,depending on the implementation, a moving status, a stationary status,an accelerating status, and/or a decelerating status of the logisticscontainer. For example, if logistics container 31700A is being moved,but is on a transport or conveyance that is slowing down, one or more ofmotion sensors 41465 a-c as shown in FIG. 42 will detect a deceleratingmotion status for container 31700A and report this to the nodeprocessing unit within container node 41000. In another example, wheredoor 37205 is being opened, motion sensor 41465 a sense movement of thedoor 37205 and will report a moving status (e.g., logistics containerdoor movement) to the node processing unit as the detected motion statusof the container 31700A

In general, the motion sensing container node collectively operates toprovide information about the container's motion status back to thecontainer node's processing unit so that such information may be used toalter how the container node communicates with other nodes within awireless node network (such as package ID nodes or master nodes). Inparticular, the node processing unit 41400 of node 41000, when executingthe motion-based management code 41500 maintained on the memory storage41415/41420, becomes specially programmed and thus operative to performa series of unconventional and innovative functions as part ofmonitoring and reporting on the logistics container's motion status.Specifically, an embodiment of processing unit 41400 becomes operative,under control of at least the motion-based management code 41500, toreceive the detected motion status from the motion sensor; store thedetected motion status in the memory storage as a first motion statusfor the logistics container (e.g., stored as part of sensor data 450);receive a subsequent detected motion status from the motion sensor;compare the subsequent detected motion status to the first detectedmotion status for the logistics container; identify a changed motioncondition for the logistics container based upon the comparison of thesubsequent detected motion status and the first detected motion status;alter one or more operational communication parameters defined in thebroadcast profile based upon the identified changed motion condition;and causing the communication interface to communicate with the secondnode in accordance with the altered operational communication parameter.Thus, an embodiment of exemplary container node 41000 has enhancedmotion-based functionality to adapt how it communicates based ondetection of the container's motion status.

The broadcast profile maintained on the memory storage may beimplemented as one of several communication mode profiles (such as oneof broadcast profiles 41330). As such, each of the communication modeprofiles may define respectively different variations of the operationalcommunication parameter used by the relevant communication interface onthe container node when broadcasting a signal in an attempt tocommunicate with the second node. For example, revising an operationalcommunication parameter may involve changing broadcast profiles suchthat an exemplary container node with a ULD container may essentiallychoose a “sleep/stationary” broadcast profile that broadcasts lessfrequently over a “moving” broadcast profile that may broadcast morefrequently given a changed motion condition identified by the containernode related to the ULD's motion status. However, in an embodiment usinga single broadcast profile, an exemplary embodiment having a containernode within a ULD container may be enabled to alter its broadcastprofile by revising an operational communication parameter to broadcastless frequently when stationary or broadcast more frequently when movinggiven the changed motion condition identified by the container noderelated to the ULD's motion status.

In a more detailed embodiment, the node processing unit may alter theoperational communication parameter by revising the operationalcommunication parameter of the broadcast profile stored in the memorystorage, where the revised operational communication parameter relatesto how the container node communicates with the second node inaccordance with the identified changed motion condition for thelogistics container. Such a second node, in this more detailedembodiment, may be implemented with a server (e.g., server 100) managinga wireless node network that includes the container node apparatus; afacility master node (e.g., facility master node 37110 a) managing thecontainer node and in communication with a server managing a wirelessnode network that includes the container node apparatus and the facilitymaster node; and/or a package ID node (e.g., ID node A 38120A)associated with a package maintained within the logistics container.

In even more detail, the revised operational communication parameter ofthe broadcast profile may be implemented in an embodiment to change apower level of a signal broadcast by the communication interface. Inother embodiments, the revised operational communication parameter ofthe broadcast profile may change how frequently the node processing unitcauses the communication interface to communicate with the second node.For example, when the changed motion condition indicates the logisticscontainer is at least stationary or decelerating, the revisedoperational communication parameter of the broadcast profile maydecrease how frequently the node processing unit causes thecommunication interface to communicate with the second node. In anotherexample, after (a) the changed motion condition previously indicated thelogistics container was stationary or decelerating and (b) a currentchanged motion condition indicates the logistics container is now movingor accelerating, the node processing unit may change the revisedoperational communication parameter to increase how frequently thecontainer node communicates with the second node. And in yet anotherexample, when the changed motion condition indicates the logisticscontainer is at least one of moving or accelerating, the revisedoperational communication parameter of the broadcast profile mayincrease how frequently the node processing unit causes thecommunication interface to communicate with the second node. Thus,various embodiments may be deployed to adaptively change how thecontainer node communicates with other nodes and based upon differenttypes of changed motion conditions.

In a further embodiment, the communication interface on the containernode apparatus may respond to input or instructions from the nodeprocessing unit by transmitting a message to the second node where themessage is related to the changed motion condition of the logisticscontainer. In this further embodiment, the second node may beimplemented with at least one or a server, a master node, and a packageID node associated with a package maintained within the logisticscontainer. Further still, the communication interface may be implementedas a long range interface (e.g., medium/long range communicationinterface 41485) operative to provide access to a server as the secondnode or a short range interface (e.g., short range communicationinterface 41480) operative to provide access to a package ID node as thesecond node, where such a package ID node is associated with a packagemaintained within the logistics container (e.g., such as package ID NodeA 38120A associated with package 38100A maintained within logisticscontainer 37100A).

When the communication interface is implemented as the short rangeinterface (such as short range communication interface 41480 that maycommunicate using BLE formatted signals), the node processing unit maybe further operative to cause the short range interface to transmit acontrol message to the package ID node. Such a control message mayprovide instructional input to the package ID node that alters operationof the package ID node based upon the identified changed motioncondition of the logistics container. Thus, detected motion statusrelated to the container may be used by multiple nodes to change notonly the communication operation of the container node attached to thelogistics container, but also to a package ID node within a packagemaintained with the same logistics container.

As shown in FIGS. 42 and 41 and described above, exemplarymotion-sensing container node 41000 may be operational as an apparatusitself in an embodiment where the node is attached to a logisticscontainer, such as container 37100A. FIGS. 41 and 42 also illustrate afurther embodiment that focuses on using exemplary motion-sensingcontainer node 41000 as a component of an exemplary motion sensingcontainer apparatus. Such an embodiment of an exemplary motion sensingcontainer apparatus generally includes both a logistics container (e.g.,container 37100A) and a container node (e.g., node 41000) together wherethe container node is attached to the logistics container (e.g., fixedto, integrated as part of, or temporarily mounted to the container).

In this container apparatus embodiment, the logistics containermaintains a plurality of packages (e.g., packages 38100A-38100D) withina housing portion having an opening that may be secured by a doorportion movably coupled to the housing portion. In particular, thehousing defines an interior storage area capable of maintaining thepackages. The door secures the interior storage area when in a closedposition relative to the housing, and provides access through theopening to the interior storage area when the door is in an openposition relative to the housing.

An exemplary logistics container may be in a variety of forms in thiscontainer apparatus embodiment. For example, the logistics containermay, in more detail, be implemented using a ULD container that may bespecially designed and configured to be shipped on aircraft; anintermodal shipping container that is, for example, specially outfittedto be transported on a container ship and be transferred as a loadedunit for further transport on another mode of transportation (e.g., viarailway or highway conveyance); a trailer that may be designed to bepulled behind a truck; a delivery vehicle that may be loaded and fromwhich deliveries are made over land, air, and water; a secure drop boxlogistics receptacle; and a secure locker container. Each of suchexemplary types of logistics container may be exposed to differentmotion stimulus, which may allow for a highly tuned and adaptive way ofaltering how an exemplary container node attached to or associated withthe container may autonomously operate to change a communication profilewhen communicating with other nodes.

The exemplary container node attached to such a logistics container aspart of this motion-sensing container apparatus embodiment may be afirst node in a wireless node network. Consistent with what is explainedabove with respect to exemplary container node 41000, the container nodein the motion-sensing container apparatus embodiment includes at least amotion sensor that detects a motion status of the logistics container,and a communication interface operative to allow the container node tocommunicate with a second node in the wireless node network inaccordance with the container node's motion-dependent broadcast profilebased upon the motion status detected by the motion sensor.

In more detail, the motion sensor in such a motion-sensing containerapparatus embodiment may be implemented with different types of motionsensors, such as an inertial sensor, a shock detector, an accelerometer,and a microelectromechanical (MEMS) sensor. The detected motion statusfrom the motion sensor in this apparatus embodiment may include a movingstatus, a stationary status, an accelerating status, and/or adecelerating status of the container.

The motion sensor in such a motion-sensing container apparatusembodiment may also be implemented with one or more similar or differingmotion sensing elements. Thus, when the exemplary motion sensor in thiscontainer apparatus embodiment uses multiple sensing elements, at leastone of the motion sensing elements may deployed relative to the doorportion of the logistics container to sense movement of the door portion(such as when logistics personnel or other personnel open or close thedoor). Motion-based detection of access to within the logisticscontainer (based on one of the motion sensing elements attached to thecontainer's door in one embodiment) provides a self-detected stimulusthat can be advantageously used by the container apparatus' containernode to at least change how it broadcasts.

Further embodiments may have one of the motion sensing elements deployedto sense movement of the door in more specific ways. For example,various embodiments of such a motion sensing element may be implementedas an inertial sensor sensitive to inertial motion of the door; anoptical sensor sensitive to light from outside the logistics containerwhen the door is in the open position; a proximity sensor sensitive to adetected distance to the door so that opening the door results in adifferent detected distance to the door; an infrared sensor sensitive tomotion of the door portion; a microwave sensor sensitive to motion ofthe door; an ultrasonic sensor sensitive to motion of the door; or animage sensor operative to capture image information over time of thedoor and, based upon analysis of the captured image over time, to detectmotion of the door.

As noted above, the communication interface of the motion-sensingcontainer apparatus embodiment's container node allows the containernode to communicate via the motion-dependent broadcast profile with asecond node. Examples of such a second node may include a server (e.g.,server 100 as shown in FIG. 42) managing the wireless node network thatincludes the container node; a facility master node (e.g., facilitymaster node 37110 a as shown in FIG. 42) managing the container node andin communication with a server managing the wireless node network thatincludes the container node and the facility master node; or a packageID node (e.g., ID node A 38120A associated with package 38100A as shownin FIG. 42) associated with at least one of the packages maintainedwithin the interior storage area of the logistics container.

Further embodiments of the motion-sensing container apparatus includemore details of the motion-dependent broadcast profile. For example, themotion-dependent broadcast profile may be implemented as an operationalnode profile that changes how frequently the communication interfacecommunicates with the second node based upon the motion status detectedby the motion sensor. In another example, the motion-dependent broadcastprofile may be implemented to decrease how frequently the communicationinterface communicates with the second node when the motion statusdetected by the motion sensor indicates the logistics container is atleast one of stationary or decelerating. Furthermore, themotion-dependent broadcast profile may be implemented to increase howfrequently the communication interface communicates with the second nodewhen the motion status detected by the motion sensor indicates thelogistics container is at least one of moving or accelerating. And inyet another embodiment, the motion-dependent broadcast profile may beimplemented so as to change a power level of a signal broadcast by thecommunication interface based upon the motion status detected by themotion sensor.

The container node's communication interface in the motion sensingcontainer apparatus may also take different forms in variousembodiments. In one embodiment, the communication interface comprises along range interface (such as medium/long range communication interface41485) operative to provide access to a server as the second node. Sucha long range interface may provide such access via a longer rangecommunication protocol, such as with communications using Wi-Fi orcellular formats. However, in another embodiment, the communicationinterface may be a short range interface (such as short rangecommunication interface 41480) operative to provide access to a packageID node as the second node, where the package ID node is associated withat least one of the packages maintained within the interior storage areaof the logistics container. In more detail, such an embodiment of theshort range interface may transmit a control message to the package IDnode according to a short range communication protocol (such as BLE)based upon the motion status detected by the motion sensor in accordancewith the motion-dependent broadcast profile. As such, the controlmessage may provide an instructional input or command to the package IDnode so as to alter operation of the package ID node.

The exemplary container node may also be deployed as a component in anexemplary motion-based management system for a logistics containermaintaining a plurality of packages within the logistics container. Thisexemplary system embodiment essentially includes a plurality of packageID nodes and a container node associated with the logistics container.Each of the package ID nodes (e.g., ID nodes A-D 38120A-D) is associatedwith a different one of the packages (e.g., packages 38100A-D)maintained within the logistics container. The container node in thissystem embodiment comprises at least a motion sensor and a communicationinterface. The motion sensor of the container node operates to detect amotion status of the logistics container, while the communicationinterface operates to allow the container node to communicate with atleast one of the package ID nodes in accordance with a motion-dependentbroadcast profile based upon the motion status detected by the motionsensor. Thus, this particular system embodiment focuses on the hierarchyof a motion-sensitive container node and the package ID nodes asdisposed within a logistics container.

In this systems embodiment, the motion sensor may be configured similarto that described above relative to the motion-sensing containerapparatus embodiment where the detected motion status for the logisticscontainer may be at least one of a moving status, a stationary status,an accelerating status, and a decelerating status. In particular, such amotion sensor of the container node may be implemented as, for example,an inertial sensor, a shock detector, an accelerometer, and amicroelectromechanical (MEMS) sensor. And such a motion sensor may beimplemented with one sensing element or multiple sensing elements. Inone embodiment where at least one of the motion sensing elements isdeployed relative to an access door on the logistics container to sensemovement of the access door, the motion sensor may detect the motionstatus by detecting movement from the door-deployed sensing element(s).Such motion sensing element or elements deployed to sense movement ofthe access door may, for example be implemented as at least one of aninertial sensor sensitive to inertial motion of the access door; anoptical sensor sensitive to light from outside the logistics containerwhen the access door is in the open position; a proximity sensorsensitive to a detected distance to the access door; an infrared sensorsensitive to motion of the access door; a microwave sensor sensitive tomotion of the access door; an ultrasonic sensor sensitive to motion ofthe access door, and an image sensor operative to capture imageinformation over time of the access door to detect motion of the accessdoor.

Further embodiments of the motion-based management system may includemore details of the motion-dependent broadcast profile. For example, themotion-dependent broadcast profile in such a system embodiment may beimplemented as an operational node profile that can change howfrequently the communication interface communicates with one of thepackage ID nodes based upon the motion status detected by the motionsensor. In another example, the motion-dependent broadcast profile insuch a system embodiment may decrease how frequently the communicationinterface communicates with one of the package ID nodes when the motionstatus detected by the motion sensor indicates the logistics containeris at least one of stationary or decelerating. In still another example,the motion-dependent broadcast profile may increase how frequently thecommunication interface communicates with one of the package ID nodeswhen the motion status detected by the motion sensor indicates thelogistics container is at least one of moving or accelerating.Additionally, a further embodiment may have the container node beingoperative to transmit a control message to one of the package ID nodesbased upon the motion status detected by the motion sensor in accordancewith the motion-dependent broadcast profile. Such a control messageprovide instructional input to the package ID node so as to alter theoperation of the package ID node (e.g., having the package ID node shiftto a “sleep” mode to converse battery life while the system's containernode detects a stationary motion status).

Further embodiments of the motion-based management system may alsoinclude more details of the communication interface on the system'scontainer node. For example, the communication interface may also beoperative to allow the container node to communicate with a higher levelnode apparatus (in addition to communicating with a package ID node).This may be implemented with two different communication interfaces(such as interfaces 41480 and 41485); with a single communicationinterface that logically includes one interface to communicate with apackage ID node and another interface to communicate with the higherlevel node apparatus (such as a facility master node); or a singlecommunication interface that may communicate with both a package ID nodeand the higher level node apparatus over the same communication path(e.g., using BLE communications for container node's interface 41480 tocommunicate with both ID node A 38120A and facility master node 37110 awhen container node 41000 and facility master node 37110 a are closeenough for such communications).

Further embodiments of this motion-based management system for alogistics container may also provide more detailed implementations onthe motion-dependent broadcast profile of the system's container node.For example, the motion-dependent broadcast profile may change a powerlevel of a signal broadcast by the communication interface based uponthe motion status detected by the motion sensor. In another example, themotion-dependent broadcast profile of the system's container node mayalso change how frequently the communication interface communicates withthe higher level node apparatus based upon the motion status detected bythe motion sensor (e.g., may decrease how frequently the communicationinterface communicates with the higher level node apparatus when themotion status detected by the motion sensor indicates the logisticscontainer is at least one of stationary or decelerating or may increasehow frequently the communication interface communicates with the higherlevel node apparatus when the motion status detected by the motionsensor indicates the logistics container is at least one of moving oraccelerating.

A further embodiment may implement the higher level node apparatus witha server in direct communication with the container node via thecommunication interface. Another embodiment may implement the higherlevel node apparatus with a facility master node in direct communicationwith the container node via the communication interface, where thefacility master node is managed by a server on a still higher level ofthe network. Thus, the communication interface recited in the system'scontainer node may be implemented to communicate with various types ofhigher level node apparatus devices.

Expanding further, additional embodiments of an exemplary motion-basedmanagement system as explained above may expressly include a server indirect communication with the container node via the communicationinterface and/or a facility master node in direct communication with thecontainer node via the communication interface, where the facilitymaster node is also in communication with a server and managed by theserver.

As described above, an exemplary container node (such as node 41000illustrated in FIGS. 41 and 42) may operate as a component in variousapparatus as well as more complex systems of components that implementdevices used for motion-based management of a logistics container. FIG.43 is a flow diagram illustrating an exemplary method more explicitlyfocused on the operation of such an exemplary container node whenperforming motion-based management of a logistics container inaccordance with an embodiment of the invention. Referring now to FIG.43, exemplary method 4300 begins at step 4305 with monitoring thelogistics container using a motion sensor of the container node. Moredetailed embodiments may implement the motion sensor used in step 4305with, for example, an inertial sensor, a shock detector, anaccelerometer, or a microelectromechanical (MEMS) sensor. Such a motionsensor, as noted previously, may comprise one or multiple sensingelements (of the same type of sensing element or of a diverse mixture ofdifferent types of sensing elements suitable for the particular part ofthe logistics container being monitored).

At step 4310, method 4300 continues with detecting a motion status forthe logistics container by the container node's motion sensor. Such amotion status may be reflected a movement detected (or no longerdetected) to indicate and reflect a moving status, a stationary status,an accelerating status, or a decelerating status for the logisticscontainer. In a more detailed embodiment where at least one sensingelement is attached to a door portion of the logistics container tosense movement of the door portion, the motion sensor may detects themotion status by detecting movement from at least the door relatedsensing element.

At step 4315, method 4300 stores the current detected motion status forthe logistics container within memory storage of the container node. Forexample, node processing unit 41400 may store the current detectedmotion status information received from motion sensor 41465 as part ofsensor data 450 within its memory structures (e.g., memory storage 41415and/or volatile memory 41420) as well as prior motion status informationfor the logistics from previous movement events related to the logisticscontainer detected with the motion sensor. In another example, themotion sensor itself may implement a type of memory storage that isoperative to locally store the current detected motion statusinformation as well as prior motion status information.

At step 4320, method 4300 proceeds to have the container node comparingthe detected motion status to a prior motion status for the logisticscontainer maintained in the memory storage of the container node. Thismay, for example, be performed by the container node's processing unit(e.g., unit 41400). However, in another embodiment, this step may beperformed locally within a motion sensor that may implement a local typeof memory storage, as noted above, and have onboard logic that canlocally compare different detected motion-related information (e.g.,measurement values commensurate and corresponding to movementexperienced by the logistics container).

At step 4325, method 4300 continues with the container node identifyinga changed motion condition for the logistics container based upon thecomparison of the detected motion status and the prior motion status. Ina more detail embodiment of step 4325, when the current detected motionstatus information changes by a threshold amount when compared to aprior motion status information, then the container node may identify achanged motion condition (which will depend upon the particularcurrently detected motion status and the prior detected motion status).For example, logistics container 31700A may initially be stationary, butmay be picked up and placed on a moving conveyor system. The containernode 41000 attached to logistics container 31700A may compare (as partof an example of step 4325) a detected motion status related to thecontainer (i.e., a moving status reflected by the motion sensor 41465 oncontainer node 41000) to a previously detected and prior motion statusfor the same container (i.e., a stationary status reflected by the samemotion sensor 41465).

At step 4330, method 4300 proceeds with altering a broadcast profile forthe container node based upon the changed motion condition for thelogistics container. In this particular way, the container node and itsvarious components may operate according to method 4300 to yield atechnical result that autonomously has the container node responsivelychanging aspects of its own broadcast profile using its own motion-basedmonitoring without relying upon a higher level node or server to causesuch changes. In a further embodiment of step 4330, method 4300 may havethe container node revising at least one parameter of the broadcastprofile to change how the container node communicates with a second node(such as a server managing a wireless node network that includes thecontainer node; a facility master node managing the container node andin communication with a server managing a wireless node network thatincludes the container node and the facility master node; or a packageID node associated with a package maintained within the logisticscontainer). The revised parameter may, in some embodiments, change howfrequently the container node communicates with the second node basedupon the revised parameter of the broadcast profile. For example, therevised parameter may cause the container node to decrease howfrequently the container node communicates with the second node when thechanged motion condition indicates the logistics container is at leastone of stationary or decelerating. In more detail, the revised parametermay cause the container node to increase how frequently the containernode communicates with the second node after the changed motioncondition previously indicated the logistics container is at least oneof stationary or decelerating but a current changed motion conditionindicates the logistics container is at least one of moving oraccelerating. In still another example, the revised parameter may causethe container node to increase how frequently the container nodecommunicates with the second node when the changed motion conditionindicates the logistics container is at least one of moving oraccelerating. And in yet another example, the revised parameter maycause the container node to change a power level of a signal broadcastby the container node based upon the revised parameter of the broadcastprofile.

As previously described with respect to other above-describedembodiments, further embodiments of step 4330 in method 4300 may involvemore than one stored broadcast or communication mode profiles (e.g.,such as broadcast profiles 41330). As such, altering the broadcastprofile may be implemented in such an embodiment by selecting frommultiple communication mode profiles (e.g., broadcast profiles 41330)based upon the changed motion condition when the container nodeidentifies the changed motion condition. Each of the communication modeprofiles defines a different set of operational parameters used by thecontainer node when broadcasts a signal in an attempt to communicatewith a second node, such as parameters that may be used when thecontainer is airborne, when the container is being unloaded, and otherlogistics-oriented situations.

An embodiment of method 4300 may proceed directly from step 4330 back tostep 4305 to begin monitoring again for another movement type of event(e.g., a drop, shock, impact, vibration, acceleration, deceleration,door opening, door closing, movement, or simply a lack of movement).However, a further embodiment of method 4300 may, at step 4335, have thecontainer node notify a second node in a wireless node network (e.g., aserver, a master node, and/or a package ID node associated with apackage maintained within the logistics container) with a messagerelated to the changed motion condition of the logistics containerbefore proceeding back to step 4305.

In more detail, another embodiment of method 4300 may have the containernode operating to specifically transmit a control message to a packageID node associated with a package maintained within the logisticscontainer. The control message provides, in this embodiment,instructional input (e.g., commands, data, or other relevant operationalinformation) to the package ID node that changes a communication profilefor the package ID node relative to the identified changed motioncondition of the logistics container. Thus, an expanded method 4300 mayleverage the container node as both altering its own broadcast profilebut also being able to alter a communication profile for one or more ofthe package ID nodes being managed by the container node and as disposedwithin packages maintained within the logistics container.

While FIGS. 37, 38, and 42 describe aspects of an exemplary logisticscontainer 37100A that may be accessible by a door or other re-sealableor opening/closing structure so as to seal off the interior of thecontainer, FIGS. 44-53 illustrate aspects of another type of logisticscontainer that may also be used with an exemplary container node asdescribed above. In general, the type of logistics container describedin FIGS. 44-53 involves a node-enhanced base platform that supportspackages and/or unpackaged items being transported and a cover for thebase platform. Collectively as an assembled unit, the node-enhanced baseand cover hold and maintain packages together in a secure manner. Such atwo-part container essentially functions similar to a ULD type oflogistics container in that both types of container hold and maintainpackages for transport. However, as discussed in more detail below, thisalternative type of logistics container (i.e., a base platform type oflogistics container) may use a particular type of container node withfurther sensors on it.

In more detail, FIG. 44 is a diagram illustrating an exemplary baseplatform used as part of an alternative embodiment of a logisticscontainer in accordance with an embodiment of the invention. Referringnow to FIG. 44, exemplary base platform 4400 is illustrated inperspective to show a central support surface 4405 surrounded by railtype of edge structure 4410 on the periphery of the base platform 4400.As explained further and shown in FIGS. 52 and 53, the base platform4400 (via its central support surface 4405) is capable of supportingmultiple packages via its central support surface 4405. In oneembodiment, the central support surface 4405 may be implemented as arigid skid such that the rail structure 4410 is disposed along itsperiphery as a foundation to which multiple base attachment points maybe installed and deployed. Further embodiments of base platform 4400 maybe implemented as pallet-based platforms that may be configured to nestor stack, and made from a variety of materials (e.g., metal, wood,plastic, etc.) of sufficient strength to support what is targeted to beshipped on its central support surface while allowing for baseattachment points along its periphery that mate with parts of a cover(e.g., grommet-lined edges of a cargo net or connection clips used atdispersed points of the cover's edge).

The exemplary rail edge structure 4410 is shown having respectivechannels 4415 a-4415 d within its rail structure between each of thecorners 4420 a-4420 d. The channels 4415 a-4415 d essentially provide agrooved slot-like location outside the central support base surface 4405and near the periphery of the base platform. In this embodiment, it iswithin such channels 4415 a-4415 d where base attachment points may bemounted in various ways (such as those shown in FIGS. 48-49) and wherean exemplary container node may be mounted (as shown in more detail inFIGS. 45, 50 and 51). In other embodiments, the rail structure itselfmay incorporate integrated base attachment points (such as eye-likeholding points shown in FIGS. 48-49). Likewise, in other embodiments,the container node may be integrated as part of the base platformitself.

FIG. 45 is a close up diagram illustrating further details of a cornerof the exemplary base platform 4400 shown in FIG. 44 in accordance withan embodiment of the invention. Referring now to FIG. 45, the rail edgestructure 4410 on the periphery of the base platform 4400 shows where anexemplary container node 44200 may be attached within one of thechannels 4415 c. In some embodiments, the entire container node 44200(including all sensors and antennas) is localized to a small singlelocation within a part of the base platform (such as being attachedwithin channel 4415 c next to corner 4420 c). However, in otherembodiments, container node 44200 may be deployed having a centralhousing located and attached to one part of the base platform (e.g.,within channel 4415 c next to corner 4420 c) and multiple sensors and/orantenna elements dispersed at other parts of the base platform 4400. Forexample, an embodiment of container node 44200 may have one or moresensors and/or one or more antenna elements that may be, for example,disposed within each of channels 4415 a-4415 c, disposed proximate eachof corners 4420 a-4420 c, and/or integrated into the central supportbase surface 4405 so as to provide a more robust reception fieldrelative to the base platform 4400 capable of localizing signals nearby(e.g., within node-enabled packages supported by surface 4405).

As deployed relative to base platform 4400, exemplary container node44200 is used as a node in a wireless node network of devices (similarto container node 4100 within the wireless node network of devices shownin FIG. 42). Container node 44200 (as shown on FIGS. 45, 50 and 51) issimilarly configured to exemplary container node 41000 (as shown andexplained relative to FIG. 41) and has at least a motion sensor and acommunication interface. The motion sensor of node 44200 (similar tomotion sensor 41465 of node 41000) may have one or more sensing elementsand operates to detect a motion status of the logistics container madeup of the base platform and a cover secured in place relative to theplatform. The communication interface that operates to allow thecontainer node 44200 to communicate with a second node in the wirelessnode network in accordance with a motion-dependent broadcast profile(such as one or more of broadcast profiles 41330) based upon the motionstatus detected by the motion sensor of node 44200 (e.g., whether thecontainer using base platform 4400 is detected as having a movingstatus, a stationary status, an accelerating status, or a deceleratingstatus).

As noted with container node 41000, exemplary container node 44200 mayalso include further sensors (such as the other sensors 41467 describedwith node 41000 shown in FIG. 41) that are operatively coupled to thenode's processing unit. Thus, in one embodiment, container node 44200may include a magnetometer type of additional sensor (e.g., sensor41467) that measures a magnetic field strength proximate the logisticscontainer (i.e., the combined base platform and its secured cover). Insuch an embodiment, the communication interface may also allow thewireless container node to communicate with the second node inaccordance with the motion-dependent broadcast profile further basedupon the measured magnetic field strength. Stated another way in moredetail, the container node may communicate with the second node via thecommunication interface in accordance with the motion-dependentbroadcast profile and further based upon a change in magnetic fieldstrength as measured by the magnetometer over a period of time. Thus, anembodiment of container node 44200 that deploys a magnetometer inaddition to the motion sensor provides a type of motion and magneticsensing container apparatus that is autonomously responsive to movement(via detected acceleration) and changes in the magnetic field exposed tothe container.

FIGS. 46 and 47 show different configurations for typical channels inthe base platform's rail structured periphery. In particular, FIG. 46 isa diagram illustrating a cross-sectional view of a first exemplary typeof periphery edge piece from the exemplary base platform shown in FIG.44 in accordance with an embodiment of the invention. Referring now toFIG. 46, the illustrated A-A′ sectional view relative to FIG. 45 isshown in cross-section with channel 4415 b as a straight slot-likechannel structure that has periodically disposed holes 4430 through thebottom of the channel 4415 b. FIG. 47 shows a cross-sectional view of asecond exemplary configuration for periphery edge structure 4410 wherethe channel 4415 b′ is configured with a retaining style slot channelstructure with periodically disposed holes 4430 through the bottom ofchannel 4415 b′. Such a retaining style slot channel structure includescaptive overhanging flanges 4435 that operate to hold items placedwithin the channel 4415 b′.

In general, the channels on periphery 4410 allow for insertable baseattachment points (e.g., movable eye structures that may be selectivelysecured in place) to be used along the periphery 44100 so that a covermay be secured in place with such attachment points. FIGS. 48 and 49show different configurations of exemplary base attachment points asdisposed and attached relative to these different configurations ofchannels 4415 b, 4415 b′ of base platform 4400. For example, FIG. 48shows a cross-sectional view of an exemplary base attachment point asmated to channel 4415 b as shown in FIG. 46. This embodiment ofexemplary base attachment point is shown with an eyelet 4440 and base4445 that fit within channel 4415 b. Attached to base 4445 is a post4450 and securing hardware 4455 that allow post 4450 to be kept withinthe relative hole 4430 within the channel 4415 b. In some embodiments,post 4450 and securing hardware 4455 may be implemented as a threadedbolt and nut combination. In still other embodiments, hole 4430 may bethreaded to receive a threaded version of post 4450 (which then may notrequire further securing hardware 4455). Those skilled in the art willappreciate that other embodiments may implement post 4450 and securinghardware 4455 via other types of mechanically captive structure thatsecures eyelet 4440 and base 4445 in place relative to the periphery4410 of base platform 4400.

FIG. 49 is a diagram illustrating a cross-sectional view of anotherexemplary base attachment point used with the second exemplary type ofperiphery edge piece from the exemplary base platform shown in FIG. 47in accordance with an embodiment of the invention. Referring now to FIG.49, a similar eyelet and base 4455 is shown configured with anattachment flange 4460 and post 4465, which mate with the configurationof channel 4415 b′ including overhanging flanges 4435 and hole 4430. Inthis embodiment, post 4465 may be spring loaded to retract within base4445 such that the attachment flange structure 4460 may selectivelyslide within channel 4415 b′ to a desired position, where post 4465 maythen extend into hole 4430 as another exemplary way to secure the eyelet440 in place relative to the periphery 4410 of base platform 4400.

In like manner, FIGS. 50 and 51 show how container node 44200 may beattached to base platform 4400 via the differently configured channels.As shown in perspective in FIG. 45, exemplary container node 44200 isattached to base platform 4400 within channel 4415 c near corner 4420 c.FIG. 50 is a diagram illustrating a cross-sectional view of exemplarycontainer node 44200 as attached via a threaded screw 4470 within theconfiguration of channel 4415 c (similar to that shown as channel 4415 bin FIG. 46). While node 44200 is shown attached to base platform 4400,other embodiments may have node 44200 attached in other ways (e.g.,glued, clamped, etc.) that may be permanent or temporary so that node44200 may be removed or replaced. Further embodiments may have node44200 configured with base platform 4400 in a more integrated mannerwhere the node 44200 is built into the platform's structure. In otherwords, exemplary container node 44200 may be removably secured to thebase platform or, in some embodiments, be integrated as part of the baseplatform. Likewise, exemplary container node 44200 may be implementedusing an attachment flange 4460 and post 4470 as shown in theconfiguration of the base platform's channel (similar to that shown andexplained relative to FIG. 47).

FIG. 52 is a diagram illustrating how a plurality of exemplary packagesmay be disposed relative to the base platform 4400 shown in FIG. 44 whenthe base platform 4400 is part of an exemplary motion sensing containerin accordance with an embodiment of the invention. Referring now to FIG.52, exemplary packages 5200 a-5200 e are shown loaded or otherwisedisposed on top of the central support surface 4405 of base platform4400. Once in this configuration, an exemplary cover 5300 may bedeployed over the packages 5200 a-5200 e as shown in FIG. 53. Ingeneral, the cover 530 operates as a type of cargo restraint system thatis attached to the base platform. As shown in FIG. 53, exemplary cover5300 includes multiple cover attachment points that can be at leasttemporarily secure to base attachment points on edges of the baseplatform. For example, and as shown in FIG. 53, cover 5300 is deployedas a flexible cover (e.g., a cargo net, webbing, braided net, reinforcedtarp, and the like) with multiple tie-down straps 5305 (used as coverattachment points) that connect to base attachment points deployedwithin channels 4415 a-4415 d along the entire edge of base platform4400. When secured to the base attachment points via such straps 5305,the cover 5300 is capable of securing the plurality of packages 5200a-5200 e to the base platform 4400.

As assembled and shown in FIG. 53, the alternative embodiment of alogistics container (i.e., base platform 4400 and flexible cover 5300secured with straps 5350) may be deployed with exemplary container node44200 (as shown in FIG. 45) to make up an embodiment of a motion sensingcontainer apparatus able to communicate with other nodes. Examples ofsuch other nodes may include a server managing the wireless node networkthat includes the container node 44200; a facility master node managingthe container node 44200 and in communication with a server managing thewireless node network that includes the container node 44200 and thefacility master node; or a package ID node associated with at least oneof the packages 5200 a-5200 e supported by the base platform 44200 ofthe logistics container and secured in place with the flexible cover5300 of the logistics container.

Like container node 41000 as shown and explained above relative to FIGS.41 and 42, the container node 44200 deployed as part of this embodimentof a motion sensing container apparatus may have its motion-dependentbroadcast profile changing how frequently the communication interface ofnode 44200 communicates with the second node based upon at least one ofthe motion status detected by the motion sensor and the magnetic fieldstrength measured by the magnetometer. In more detail, themotion-dependent broadcast profile may decrease how frequently thecommunication interface of node 44200 communicates with the second nodewhen at least one of the motion status detected by the motion sensor andthe magnetic field strength measured by the magnetometer indicates thelogistics container is at least one of stationary or decelerating. Themotion-dependent broadcast profile for node 44200 may also increase howfrequently the communication interface of node 44200 communicates withthe second node when at least one of the motion status detected by themotion sensor and the magnetic field strength measured by themagnetometer indicates the logistics container is at least one of movingor accelerating. In a further embodiment, the motion-dependent broadcastprofile of node 44200 may change a power level of a signal broadcast bythe node's communication interface based upon the motion status detectedby the motion sensor and/or the magnetic field strength measured by themagnetometer.

As deployed as part of this embodiment of a motion sensing containerapparatus, an embodiment of the communication interface used incontainer node 44200 may be a long range interface (such as interface41485) that provides access to a server, or may be a short rangeinterface (such as interface 41480) operative to provide access to apackage ID node associated with at least one of the packages 5200 a-5200e supported on the base platform 4400 of the logistics container. Such ashort range interface may be used in node 44200 to transmit a controlmessage (in accordance with the motion-dependent broadcast profile) tothe package ID node based upon one of the motion status detected by themotion sensor; the magnetic field strength measured by the magnetometer;or a combination of the detected motion status and magnetic fieldstrength. Such a control message may provide instructional input via,for example, a command or instruction to the package ID node to alteroperation of the package ID node (such as having the control messagecausing the package ID node increase how frequently it transmits anadvertising signal so that the container node 44200 receives morefrequent updates from the package ID node).

Enhanced Package Placement Tracking Using a Motion-Sensitive ContainerNode

While an exemplary container node may be deployed, as explained above,for motion-based (e.g., detected physical movement, detected changes inmagnetic fields) changes to how the container node communicates invarious embodiments, additional embodiments may use an exemplarycontainer node with a motion sensor (such as an accelerometer) toenhance determinations on whether a package has been placed within aparticular logistics container. In general, a container node (asdeployed with a logistics container) may detect a broadcast signal froman approaching package's ID node as the package is being loaded into thelogistics container having the container node. However, this may happenwhile other container nodes placed within other neighboring logisticscontainers also detect the broadcast signal from the package's ID node.Thus, at times, simply detecting a close signal from a package's ID nodemay not be sufficiently accurate to conclusively determine if a packagehas been placed within a particular logistics container. Accordingly, insome embodiments, a logistics container receiving the package may alsosense a bump or other impact force through sensors on the onboardcontainer node. The detected or sensed bump or impact representsplacement of the package within that particular container. Thus,detection of the broadcast signal from the package's ID node may becoupled with the detection of such a bump or impact and, collectively,used as a “tie breaker” when automatically monitoring and managingloading operations. As such, this technology-driven enhanced monitoringsolution yields a technical effect, for example, of improving howpackage placement may be tracked in a logistics container using aspecially configured and programmed container node. Stated another way,while detected information from a node-enabled and broadcasting packagemay be captured by a neighboring group of container nodes in respectivelogistics containers, the combined use of the detected impact/bump byone of the logistics containers automatically increases the confidencelevel of that package having been placed within that particularlogistics container.

FIG. 54 is a diagram illustrating an embodiment of an exemplary motionsensing container node configured for use when improved tracking ofpackages placed within a logistics container in accordance with anembodiment of the invention. Referring now to FIG. 54, exemplary motionsensing container node 54000 is shown similar to container nodes 38000and 41000 (which were earlier described as being similar in someembodiments to a master node of FIG. 4 without location circuitry). Morespecifically, those skilled in the art will appreciate that oneembodiment of exemplary container node 54000 includes many of the samehardware, code, and data components as shown for exemplary master node110 a of FIG. 4, but simplified so as not to include location circuitry,as well as to that of exemplary container node 38000 illustrated in FIG.39 and container node 41000 illustrated in FIG. 41. As such, similarfunctionality exists for what is numbered the same or similarly anddescribed above regarding exemplary master node 110 a and exemplarycontainer nodes 38000 or 41000. Thus, while master node 110 a shown inFIG. 4 is described as having processing unit 400, memory storage 415,volatile memory 420, clock/timer 460, sensors 465, battery/powerinterface 470, short range communication interface 475, and medium/longrange communication interface 480, exemplary container node 54000 mayuse similar hardware components as shown in FIG. 54. This includesprocessing unit 54400, memory storage 54415, volatile memory 54420,clock/timer 54460, sensors 54465 and 5467, battery/power interface54470, short range communication interface 54475, and medium/long rangecommunication interface 54480.

Further, the embodiment of exemplary container node 54000 illustrated inFIG. 54 deploys container control and management code 54425 (as storedin memory storage 54415 and loaded for execution by processing unit54400 in volatile memory 54420), which is similar in functionality tocontainer control and management code 38425, container control andmanagement code 41425, and master node control and management code 425described above in more detail. Such code, as previously described,generally controls the behavior of the node relating to communications(with a node advertise and query logic manager), information management(with an information control and exchange manager), power management(with a node power manager that interacts with the various communicationinterfaces, for example, to manage power consumption and broadcast poweraspects at a low level), and association management (with an associationmanager). As such, container control and management code 54425essentially operates similar to that as described above for containernode control and management code 38425 and code 41425 (and master nodecontrol management code 425 but without the need for a locationaware/capture module) but further includes motion-based package trackingprogram code 54500 for improved and enhanced motion-based tracking ofpackage placement within a logistics container as described in moredetail below with respect to methods described relative to FIGS. 56-58.Thus, an embodiment of motion-based package tracking program code 54500may be implemented as an integrated part of container control andmanagement code 54425, such as one or more programmatic functions oradditional program modules that may be called within code 54425.However, in other embodiments, the motion-based package tracking programcode 54500 used to implement the methods as described with respect toFIGS. 56-58 may be implemented separately from code 54425 in a way thatallows code 54500 to call some of the programmatic functions or programmodules described as part of code 425 to implement the steps as laid outin the methods of FIGS. 56-58 and variations of those methods asdescribed herein.

In general, exemplary motion-based package tracking code 54500 adaptsthe operation of container node 54000 such that the node detectsmotion-based events (and in many embodiments also detecting signalsbroadcast by a node-enabled package) and, based upon such detecteditems, responds in an unconventional way that automatically determineswhether a package was placed within the logistics container associatedwith container node 54000 so that the container node 54000 mayproactively report this determination up to a managing node in thenetwork. As such determinations are made, an embodiment of containernode 54000 running exemplary motion-based package tracking code 54500may also update an inventory of the related logistics container. Suchcurrent inventory information related to the logistics container may bekept as inventory data 54600 within container node 54000. In someembodiments, inventory data 54600 may be included and maintained as partof association data 440 in both of memory storage 54415 and volatilememory 54420, where the data 54600 reflects what packages have beendetermined to be associated with the logistics container related to thecontainer node 54000. However, in other embodiments, inventory data54600 may be maintained as a separate data structure from what ismaintained as association data 440.

As a measuring front end component for a motion-based package placementtracking involving a logistics container, exemplary motion sensingcontainer node 54000 includes various sensors, such as motion sensor54465 as a sensor or detector with one or more sensing elements that cancollectively detect or sense an impact force relative to that which itis attached (e.g., a logistics container or part thereof). An exemplaryimplementation of motion sensor 54465 (or other sensors 54467) mayinclude additional hardware (e.g., local sensor memory, battery backup,multiplexing hardware interfaces when using multiple sensing elements)and/or program/firmware features to manage the detection, collection,storage, and sharing of the captured motion-related sensor data (such asa sensed impact force and a notification generated by the sensor aboutthe sensed impact force). In some embodiments, motion sensor 54465 maybe implemented with several types of motion sensors or motion/movementdetectors, such as an inertial sensor, a shock detector, anaccelerometer, a microelectromechanical (MEMS) sensor, and the like. Andwhile sensor 54465 is explicitly shown in FIG. 54 as a motion sensor,those skilled in the art will appreciate that an embodiment of containernode 54000 may also include other types of sensors or detectors 54467,such as one or more magnetic sensors (e.g., a magnetometer, gyroscopicsensor, etc.), electronic sensors (e.g., a voltage sensor, currentsensor, electronic power sensor, etc.), and environmental sensors (e.g.,pressure, light, temperature, humidity, magnetic field, altitude,attitude, orientation, proximity, etc.).

Exemplary container node 54000 as shown in FIG. 54 may be deployed aloneor as part of various system embodiments providing node-implementedmotion-based enhanced tracking of package placement in a node-enabledlogistics container, such as that shown in FIG. 55. Referring now toFIG. 55, an exemplary motion-based system 5500 is shown that offersimproved tracking of packages placed within one of a group of differentnode-enabled logistics containers in accordance with an embodiment ofthe invention. In other words, exemplary motion-based system 5500deploys container nodes 54000 a-54000 c in respective ones of multiplelogistics containers 55100A-55100C, along with a master node 55110 thatwirelessly interacts with and manages the container nodes 55100A-55100Cand a server 100 that interacts with and manages the master node 55110over network 105.

In more detail, exemplary container node 54000 a is shown in FIG. 55 asan exemplary motion-based apparatus deployed in logistics container55100A for improved tracking of package placement within logisticscontainer 55100A. Logistics container 55100A is shown having a containerhousing 55200 and floor structure 55205 that, collectively, define aninterior storage area capable of maintaining packages, such as packages55130 a-55130 c. Some of these packages may be node-enabled packages(i.e., package 55130 a associated with ID node A 55120 a and package55130 b associated with ID node B 55120 b), while others may be apackage without a node associated with it (i.e., package 55130 c). Whilenot explicitly shown to avoid confusion and a cluttered diagram, thoseskilled in the art will appreciate that container 55100A may be accessedvia a doorway or other entrance structure that can be closed to seal offthe interior storage area of the container 55100A.

The container node 54000 a associated with logistics container 55100Ashown in FIG. 55 has a housing 54700, which is attached to logisticscontainer 55100A. Many of components of exemplary container node 54000 aare maintained within housing 54700. For example, consistent with whatwas discussed above and shown in FIG. 54, container node 54000 has atleast a node processing unit 54400 and memory storage 55415 disposedwithin the node housing 54700. Memory storage 54415 is accessiblycoupled to the node processing unit 54400 and maintaining at least themotion-based package tracking code 54500 for execution by the nodeprocessing unit 54400 (once loaded into volatile memory 54420).

Several other components of exemplary container node 54000 a may not becompletely maintained within node housing 54700. For example, exemplarycontainer node 54000 a includes a short range communication interface(such as interface 54480) and a medium/long range communication (such asinterface 54485) where both are operatively coupled to the nodeprocessing unit 54400. As such, the short range communication interfaceallows the container node 54000 a to communicate over a short rangecommunication path with an ID node associated with a package to beshipped (such as ID node A 55120 a associated with package 55130 a). Andthe longer range communication interface allows the container node 54000a to communicate over a long range communication path with a managingnode, such as master node 55110. These communication interfaces disposedas part of container node 54000 a may be implemented with certain parts(e.g., antennas or the entire transceiver unit and antenna (or units anddifferent antennas) collectively making up the communication interface)disposed outside of housing 54700. For example, the short rangecommunication interface may be configured with multiple radios ormultiple antenna elements with parts of or whole radio units dispersedin different parts around the interior storage area of container 55100Aso to provide a more robust reception field and enable more efficientlocalization of signals emanating from various nodes within thecontainer 55100A.

In addition to the communication interfaces, the exemplary containernode 54000 a shown in FIG. 55 further includes at least one motionsensor (such as motion sensor 54465) that can detect an impact force onthe logistics container 55100A. In response to such a detected impactforce, the motion sensor generates a reporting signal about the detectedimpact force and provides the reporting signal back to the nodeprocessing unit (i.e., processing unit 54400) within container node54000 a.

As noted above relative to FIG. 54, motion sensor 54465 may beimplemented with more than one sensing element. The sensor or even eachsensing element may include additional hardware (e.g., local sensormemory, battery backup, multiplexing hardware interfaces when usingmultiple sensing elements) and/or program/firmware features to managethe detection, collection, storage, and sharing of the capturedmotion-related sensor data (such as a sensed impact force and anotification generated by the sensor about the sensed impact force). Asshown in FIG. 55, the motion sensor for exemplary container node 54000 ais implemented with multiple sensing elements 54465 a-54465 c disposedwithin the logistics container to monitor an interior storage area ofthe logistics container 55100A. Specifically, each of the sensingelements 54465 a-54465 c may be disposed proximate to a differentportion of the interior storage area within logistics container 55100A.For example, motion sensing elements 54465 a-54464 c are each locatedrelative to different parts of floor 55205 of container 55100A. In someembodiments, an individual sensing element may sense an impact force forthe motion sensor to generate the reporting signal provided back to thenode processing unit within container node 54000 a. However, in otherembodiments, more than one of the sensing elements may collectivelydetect or sense the impact force relative to the logistics container orpart thereof.

As configured to provide enhanced multi-mode monitoring (e.g.,electronic signal communication as well as physical impact sensing),container node 54000 a provides an concretely deployed technicalsolution using unconventional functionality of the node 54000 a yieldinga technical result that improves how to monitor loading of logisticscontainer 55100A. In doing so, an embodiment of the node processing unit54400 of exemplary container node 54000 a in FIG. 55, when executing themotion-based package tracking code 54500 maintained on the memorystorage 54415 (and as loaded and running in volatile memory 54420),becomes operative to cause the short range communication interface toelectronically listen for an ID node (such as ID node A 55120 a) inaccordance with a scanning mode of the container node 54000 a. Forexample, the short range communication interface 54480 of node 54000 amay scan or listen for a BLE formatted signal being broadcast by an IDnode (such as ID node A 55120 a associated with package 55130 a) nearnode 54000 a. Detection of such a BLE formatted signal may occur as thepackage 55130 a with ID node A 55120 a is being moved towards thelogistics container 55100A (e.g., during a loading operation ofdifferent containers 55100A-55100C) prior to being actually being placedwithin container 55100A, such as upon approach to a particular one ofthe containers 55100A-55100C, and/or as the package 55130 a is beingplaced within the interior storage area of container 55100A.

Once the particular ID node is heard by the communication interface54480 via the detected signal broadcast from the ID node, the programmedprocessing unit of node 54000 a identifies a device signature of that IDnode from the signal broadcast from the ID node and detected by thecommunication interface. In more detail, an embodiment of the programmednode processing unit of node 54000 a may identify the device signatureof the ID node from, for example, at least one of a series ofincreasingly stronger signals broadcast from the ID node and detected bythe communication interface as the ID node moves closer to the containernode 54000 a.

The programmed node processing unit of container node 5400 a theninteracts with the container node's motion sensor (e.g., one or more ofsensor elements 55465 a-55465 c) to receive the reporting signal fromthe motion sensor indicating the motion sensor detected the impact forceon the logistics container 55100A after detecting the signal broadcastfrom the ID node. The reporting signal, in some embodiments, mayindicate a level of the impact force as detected by the motion sensor.

From there, the programmed node processing unit of the container node54000 a determines whether the detected signal broadcast from thepackage's ID node (such as a signal detected from the ID node A 55120 ain package 55130 a) and the detected impact force indicate the package(such as package 55130 a) was placed within the logistics container. Inan embodiment where the reported signal from the motion sensor indicatesa level of the impact force, this level is then used as a factor indetermining whether the detected signal broadcast from the package's IDnode and such a detected force impact level indicate the package wasactually placed within the specific logistics container.

In a more detailed embodiment, the node processing unit 54400 of node54000 a may also use clock/timer 54460 (or an integrated timer circuitwithin processing unit 54400) to track an elapsed time between when theshort range communication interface detects the signal broadcast fromthe ID node and when the motion sensor detects the impact force. Such anelapsed time may also be used as a monitoring-based factor when theprocessing unit determines whether the detected signal broadcast fromthe ID node and the detected impact force indicate the package wasplaced within the logistics container. For example, if the trackedelapsed time falls outside of a predetermined threshold time period, thenode processing unit 5440 of node 54000 a may determine the package wasnot placed within container 55100A associated with node 54000 a. Thus,node processing unit 54400 of container node 54000 a may be programmedand operative to intelligently monitor different activity relative tothe logistics container 55100A (e.g., a detected impact relative tocontainer 55100A, relevant electronic signals received from a package IDnode (such as 55120 a), and/or the timing related to the two sensedevents) to automatically determine whether the package was placed withincontainer 55100A.

Based upon such a multi-mode determination, the processing node ofcontainer node 54000 a then causes the longer range communicationinterface to transmit a notification to a managing node, such as masternode 55110 or even server 100. Such a notification includes at least theidentified device signature of the ID node and status informationreflecting that the detected signal and the sensed impact forceindicating the ID node associated with the package was placed within thelogistics container 54100A.

In a further embodiment of container node 54000 a, its node processingunit may then update inventory information (such as inventory data54600) maintained on the memory storage of the node 54000 a afterdetermining whether the detected signal broadcast from the ID node andthe detected impact force indicate the package was placed within thelogistics container. Such inventory information allows the containernode 54000 a to locally track the contents of the logistics container55100A.

In further embodiments, the longer range communication interface mayalso receive a confirmation message from the managing node (e.g.,managing node 55110 or server 100) and pass the confirmation message tothe node processing unit 54400 of node 54000 a. Such a confirmationmessage verifies that the package 55130 a was properly placed within thelogistics container 55100A. For example, such a message may confirm thatthe package 55130 a was supposed to be loaded within logistics container55100A and, upon receipt of such a confirmation, the node processingunit of node 54000 a may update inventory data 54600 that tracks thecontents of the logistics container 55100A.

However, in another embodiment where package 55130 a is supposed toloaded and shipped within another container (such as container 55100B),the confirmation message received by container node 54000 a in logisticscontainer 55100A may indicate that the package 55130 a just loaded was,in fact, improperly loaded within container 55100A (i.e., confirmedmisload situation relative to package 55130 a), which requires furtheraction to be taken to unload package 55130 a. In a more detailedembodiment, a misload message may then be generated by container node54000 a and transmitted to a user access device (not shown but similarto user access device 200 in FIG. 2) operating as a type of ID node andunder the operation of loading personnel involved in loading container54000 a.

With the above-described context of exemplary container node 54000 asshown in FIG. 54 and how container node 54000 a may be deployed as partof logistics container 55100A in FIG. 55, FIG. 56 is a flow diagramillustrating an exemplary motion-based method for improved tracking ofpackage placement in a logistics container using a container node (suchas node 54000 or 54000 a) associated with the logistics container inaccordance with an embodiment of the invention. Referring now to FIG.56, method 5600 begins at step 5605 with the container node activating ascanning mode to electronically listen for an ID node associated with apackage (i.e., a package ID node). For example, exemplary container node54000 a may activate a passive or active mode of operation where it isscanning or listening for other nodes. As such, when container node54000 a is scanning while passive, the node will receive advertisingdata packets, but will not acknowledge and send SCAN_REQ messages incompliance with BLE standards. However, when container node 54000 a isscanning while active, the node will receive advertising data packets,and will acknowledge receipt by sending a SCAN_REQ message in accordancewith BLE standards.

At step 5610, if the container node detects a signal broadcast from theID node associated with the package, method 5600 proceeds from step 5610to 5615. Otherwise, step 5610 continues to scan for signals broadcastfrom a package ID node, such as advertising packet signals from an IDnode.

At step 5615, an embodiment of method 5600 may have the container nodereset and start a timer. Such a timer may be used to track the elapsedtime since the detected signal to when the container node senses animpact form from its motion sensor. As discussed relative to step 5635below, such an elapsed time may also be considered when determiningwhether the package was placed within the specific logistics containerassociated with the container node.

Thus, at step 5620, method 5600 essentially enters a state where thecontainer node monitors for a sensed impact force using a motion sensoron the container node (such as motion sensor 54465 on exemplarycontainer node 54000 or any of sensor elements 54465 a-54465 c onexemplary container node 54000 a). As noted above, an exemplary motionsensor may be implemented as an inertial sensor, a shock detector, anaccelerometer, and a microelectromechanical (MEMS) sensor. In someembodiments, such as that shown in FIG. 55, the motion sensor may beimplemented with multiple sensing elements that, in further embodiments,are disposed proximate to different portions of an interior storage areawithin the logistics container (e.g., sensor elements 54465 a-54465 c onexemplary container node 54000 a are shown disposed proximate differentareas of floor 55205 of logistics container 55100A).

At step 5625, method 5600 determines whether the container node's motionsensor has sensed an impact on the logistics container after detectingthe signal broadcast from the ID node. For example, the motion sensormay report information on a level of the impact force as sensed by oneor more of the sensing elements within the interior of the logisticscontainer. If an impact force has been sensed, step 5625 proceedsdirectly to step 5635. Otherwise, step 5625 proceeds back through step5630 where an embodiment of method 5600 may have the container nodecheck to see if the elapsed time on the started timer (see step 5615)meets or exceeds a threshold time period.

At step 5635, method 5600 proceeds with the container node determiningif package is in the logistics container based upon the sensed impactforce and the detected signal. In other words, the container nodedetermines in step 5635 whether the detected signal broadcast from theID node and the sensed impact force (or level of such a sensed impactforce) indicate the package was placed within the logistics container(such as within an interior storage area of the logistics container).Thus, if the container node determines the package was placed within thelogistics container as part of step 5635, then method 5600 proceeds fromstep 5635 to step 5640. Otherwise, method 5600 proceeds from step 5635directly back to step 5610 to look for signals from another package IDnode and restart the motion-based tracking of package placement withinthe logistics container.

In a further embodiment of method 5600, step 5635 may also includedetermining whether the detected signal and the sensed impact forceindicate the package was placed within the logistics container basedupon an elapsed time between when the container node detects the signalbroadcast from the ID node and when the motion sensor senses the impactforce. In other words, the elapsed time from the timer started at step5615 allows the container node to further consider a timing aspect alongwith the existence of the two different detected events (i.e., thedetected signal broadcast from the package ID node and the sensed impactforce relative to the logistics container). For example, if a signalbroadcast from the package ID node is detected by the container node,and an impact force of sufficient magnitude is sensed via the motionsensor of the container node, and the relative timing of those events iswithin a threshold time period, the container node may automaticallydetermine that such factors indicated the package was placed within thelogistics container. Further embodiments may refine such a determinationwith a particular threshold impact force level to be detected and/or aparticular threshold signal power level to be detected. Such refinedembodiments may allow for better determination resolution in step 5635when the logistics container associated with the container node is in acrowded area with other logistics containers or in an area with multipleactively broadcasting package ID nodes.

At step 5640, an embodiment of method 5600 may have the container nodeupdating inventory information maintained on a memory storage of thecontainer node after determining whether the detected signal broadcastfrom the ID node and the detected impact force indicate the package wasplaced within the logistics container. Such inventory information (e.g.,inventory data 54600 shown within memory of exemplary container node54000) exists and may be updated to locally track the contents of thelogistics container.

At step 5645, method 5600 proceeds with the container node transmittinga notification to a managing node (such as a master node or a server inthe wireless node network). Such a notification reflects the detectedsignal and the sensed impact force, which collectively indicate thepackage was placed within the logistics container. In this way, anembodiment of method 5600 may have the container node updating acomponent higher within the network of elements, such as shown in FIG.55, with a status of a loading operation as reflected by the localdetermination of the package having been placed within the containernode's logistics container.

At step 5650, an embodiment of method 5600 may have the container nodereceiving a confirmation message from the managing node in response totransmitting the notification at step 5465. Such a confirmation messagereceived in step 5650 verifies that the package was placed within thelogistics container. The verification in the confirmation message, insome instances, may confirm the package was placed in the appropriatelogistics container, after which the inventory information on the memorystorage may be updated (rather than at step 5640). However, in otherinstances, the verification in the confirmation message may indicate thepackage has been misloaded or loaded into an inappropriate logisticscontainer. Thus, an embodiment of method 5600 may proceed to step 5660from decision step 5655 if the package has been misloaded.

At step 5660, the container node associated with the logistics containernow may take proactive and automatic steps to rectify and address thepackage misloaded situation automatically detected. As such, thecontainer node in step 5660 may generate and transmit a misload messageto a user access device (UAD—such as user device 200 shown in FIG. 2)operating as a type of ID node and under the operation of loadingpersonnel involved in loading the logistics container related to thecontainer node. The container node, as part of step 5660, may alsorevised the inventory data locally stored indicating the currentcontents of the logistics container. Thereafter, step 5660 proceeds backto step 5610 to look for signals from another package ID node.

However, if the confirmation message received at step 5650 verifies thepackage was properly loaded and was supposed to be loaded into theparticular logistics container related to the container node performingmethod 5600, method 5600 need not engage in step 5660 and simplyproceeds from step 5655 directly back to step 5610 to look for signalsfrom another package ID node.

In light of the above description of exemplary container node 54000 a asshown in FIGS. 54 and 55 and the exemplary motion-based method 5600 forimproved tracking of package placement as explained relative to FIG. 56and implemented with a container node, such as node 54000 a, a furtherembodiment of a motion-based apparatus for improved tracking of packageplacement essentially comprises both the logistics container and itsrelated container node. In general, such an embodiment may beimplemented as a container node-enabled logistics container, such aslogistics container 55100A and related container node 54000 a, and wherethe container node part of the overall apparatus operates similar tothat described above relative to method 5600 and its variants.

In more detail, an embodiment of such a motion-based apparatus forimproved tracking of package placement includes a type of logisticscontainer that maintains (at least temporarily) one or more packages(such as exemplary logistics container 55100A as shown and explained inFIG. 55) within an interior storage area for the packages. Theembodiment of the motion-based apparatus also includes a container nodeattached to the logistics container (such as exemplary container node54000 a as shown and explained relative to FIGS. 54-56). In thisembodiment, the container node further comprises a node processing unit(such as processing unit 54400), a memory storage (such as memories54415 or 54420), a motion sensor (such as motion sensor 54465 orcollectively the group of motion sensing elements 54465 a-54465 c), andtwo communication interfaces (such as interfaces 54480, 54485). Each ofthe memory storage, the motion sensor, and the two communicationinterfaces is coupled to the node processing unit of the container node.One of the communication interfaces is operative to communicate over ashort range communication path with an ID node associated with a packageto be shipped (such as ID node A 55120 a associated with package 55130a), while the second communication interface is operative to communicateover a long range communication path with a managing node (such asmaster node 55110).

The container node's motion sensor is disposed within the logisticscontainer to monitor the interior storage area of the logisticscontainer. Specifically, the motion sensor is deployed to detect animpact force on the interior storage area of the logistics container andgenerate a reporting signal about the detected impact force (such as asignal that indicates a level of the impact force detected). The motionsensor may be implemented with various types of sensors, such as aninertial sensor, a shock detector, an accelerometer, and amicroelectromechanical (MEMS) sensor. In further embodiments, thecontainer node's motion sensor may also be implemented as multiplesensing elements where each are disposed proximate to different portionsof the interior storage area of the logistics container of the overallapparatus.

The container node's memory maintains at least motion-based packagetracking node (such as code 54500) for execution by the node'sprocessing unit. As such, and when executing the motion-based packagetracking code, the container node's processing unit becomes speciallyprogrammed as part of this apparatus embodiment to provide motion-basedtracking of package placement relative to what may be loaded within thelogistics container. In more details, the container node's processingunit becomes operative to cause the first communication interface toelectronically listen for the ID node in accordance with a scanning modeof the container node apparatus and then identify a device signature ofthe ID node from a signal broadcast from the ID node and detected by thefirst communication interface. In some embodiments, identifying thedevice signal may be accomplished based upon at least one of a series ofincreasingly stronger signals broadcast from the ID node and detected bythe first communication interface. The container node's processing unitis then further operative to receive the reporting signal from themotion sensor (indicating the motion sensor has detected the impactforce on the logistics container after detecting the signal broadcastfrom the ID node) and then determine whether the detected signalbroadcast from the ID node and the detected impact force indicate thepackage was placed within the logistics container. After thisdetermination based on the multi-mode measurement input to the containernode (e.g., the detected electronic signal and the sensed impact force),the container node's processing unit is operative to cause the secondcommunication interface to transmit a notification to a managing node(such as a master node or server). The transmitted notification includesthe identified device signature of the ID node and status informationreflecting that the detected signal and the sensed impact forceindicating the ID node associated with the package was placed within thelogistics container.

In a further embodiment of the apparatus, the container node'sprocessing unit may be programmed via the motion-based package trackingcode to also track an elapsed time between when the first communicationinterface detects the signal broadcast from the ID node and when themotion sensor detects the impact force. As such and in that furtherembodiment, the container node's processing unit may be operative todetermine whether the detected signal broadcast from the ID node and thedetected impact force indicate the package was placed within thelogistics container based upon the elapsed time being within a thresholdtime period. In other words, if the two different events detectedrelative to the ID node are detected within the threshold time period,the container node's processing may indicate the package was actuallyplaced within the logistics container. Such a determination may alsodepend, in other embodiments, upon the level of the impact force asdetected by the motion sensor and indicated in the reporting signal.

Additionally, further embodiments of such an apparatus embodiment maymaintain and update an inventory for the logistics container of theapparatus. For example, the container node's processing unit may beprogrammed to update inventory information maintained on the memorystorage after determining whether the detected signal broadcast from theID node and the detected impact force indicate the package was placedwithin the logistics container. However, in another example, updatingthe inventory information may occur by the container node's processingunit after the second communication interface receives a confirmationmessage from the managing node and passes the confirmation message tothe node processing unit. Such a confirmation message verifies that thepackage was placed within the logistics container so that the containernode's processing unit waits to update inventory information trackingthe contents of the logistics container until after receiving theconfirmation message.

An even more detailed system level embodiment related to motion-basedtracking of package placement within a logistics container and methodsof its operation may involve specific operations of a master node as itinteracts with multiple exemplary container nodes as associated withrespective logistics containers. As shown in FIG. 55, exemplary masternode 55110 is disposed as a type of managing node in a network level oneup from each of container nodes 54000 a-54000 c and a network level downfrom server 100 within the exemplary motion-based system 5500. As such,exemplary master node 55110 interactively communicates with server 100and with each of container nodes 54000 a-54000 c as part of a monitoredloading operation where the container nodes can deploy motion-basedtracking of package placement functionality relative to their respectivelogistics container (as describe above relative to FIGS. 54-56).

Referring now to FIG. 55, exemplary master node 55110 is illustrated asbeing an example of master node 110 a as shown and described relative toFIG. 4 with some further refinements. In other words, the functionalityof exemplary master node 55110 may build upon similar hardware andsoftware as explained above relative to exemplary master node 110 a.More specifically, as described relative to FIG. 55 and below withregard to method 5700 as shown in FIG. 57 for motion-based tracking ofpackage placement related to a monitored loading operation of multiplelogistics containers, the particular functionality of exemplary masternode 55110 may be implemented as part of master control & managementcode 425 (as stored onboard exemplary master node 55110).

Additionally, when operating to interact and interface with variouscontainer nodes 54000 a-54000 c that deploy motion-based tracking ofpackage placement (as discussed in the various embodiments above),exemplary master node 55110 generally creates and/or stores someadditional type of data within the memory (such as memory storage 415 orvolatile memory 420) of exemplary master node 55110. For example,exemplary master node 55110 typically maintains inventory data 55570,which locally represents at least anticipated inventory informationrelative to different logistics containers. Such inventory data 55570may, in some embodiments, be generated by the master node 55110 basedupon relevant shipment data 580 provided by server 100 or may, in otherembodiments, be provided from server as anticipated inventoryinformation for a particular logistics container that is being loaded(such as containers 55100A-55100C).

As such logistics containers are being loaded with packages (whichexpressly include packaged items and non-packaged items to be shippedvia such a container), exemplary master node 55110 may generate andstore loading productivity information as productivity data 55605. Suchdata 55605, as described in more detail below, generally relates totiming of relevant tracked package placement events for particularlogistics containers and, more specifically, may indicate how quicklythe logistics container associated with a particular container node isbeing loaded as part of the monitored loading operation whenautomatically tracked using wireless node devices, such as exemplarycontainer nodes 54000 a-54000 c.

As the logistics containers 55100A-55100C are being loaded with packages(e.g., packaged items and non-packaged items to be shipped via such acontainer), exemplary master node 55110 may receive and/or accessbarcode scan data associated with particular packages. Such scan data isgenerally stored as scan data 55570 on master node 55110, which may besent to master node 55110 from server 100 (e.g., scan data 570maintained within server 100 on captured barcode information on itemsbeing shipped) or from a barcode scanning device, such as an ID nodeenabled barcode scanner 55200 used to capture barcode informationrelated to the package. Those skilled in the art will appreciate thatsuch an ID node enable barcode scanner 55200 may be implemented basedupon exemplary ID node 120 a where one of the sensors 360 may include abarcode scanner (e.g., laser-based or image capture type of device) thatextracts barcode information from an externally viewable/scannablebarcode label on a package.

FIG. 57 is a flow diagram illustrating an exemplary motion-based methodfor improved tracking of package placement relative to a plurality ofcontainer node-enabled logistics containers as part of a monitoredloading operation using a wireless node network including at least amanaging node (such as a master node or a server) in accordance with anembodiment of the invention. Referring now to FIG. 57, method 5700begins at step 5705 where a container node in each of the logisticscontainers is activated to monitor an interior package storage area ofeach of the logistics containers using at least a motion sensor on thecontainer node. Such a motion sensor may, for example, use one or moresensing elements and may collectively be implemented as an inertialsensor, a shock detector, an accelerometer, or a microelectromechanical(MEMS) sensor. When implemented with multiple sensing elements, eachsensing element of a particular motion sensor may be disposed proximateto different portions of the interior package storage area (such asproximate to different portions of floor 55205 in logistics container55100A). For example, as shown in FIG. 55, each of container nodes 54000a-54000 c may be activated, as part of system 5500, to monitor theinterior package storage area within each of their respective logisticscontainers 55100A-55100C.

At step 5710, method 5700 has the managing node receiving a detectionnotification from one of the container nodes where the detectionnotification indicates at least detection of a signal broadcast from anID node in the wireless node network and an identification of the IDnode. Such an ID node is associated with a package involved in theloading operation. For example, step 5710 may be implemented when masternode 5510 receives a detection notification from container node 54000 a,and that notification indicates detection of a signal from ID node A55120 a associated with package 55130 a and the identification of IDnode A 55120 a. In more detail, the detection notification sent tomaster node 55110 may have a device signature for ID node A 55120 aderived from the signal broadcast from the ID node A 55120 a. Such adevice signature generally operate as an identifier of the ID node, suchas MAC address or a shipment tracking number unique to the node, and maybe included in part of the signal broadcast from the ID node (such as apart of the signal's header).

At step 5715, method 5700 has the managing node receiving a sensedimpact notification as part of the detection notification received fromthe reporting one of the container nodes. The sensed impact notificationprovided as part of the notification received by the managing nodeindicates a motion sensor on the reporting container node detected animpact force on its related logistics container. Stated another way, themanaging node receives information from one of the container nodes abouta detected package ID node signal as well as a detected impact force onthe container node's logistics container as part of steps 5710 and 5715.

In a more detailed embodiment of method 5700, the sensed impactnotification received by the managing node may indicate the motionsensor on the reporting container node detected the impact force on thelogistics container associated with the reporting container node withina threshold time period after the reporting container node's short rangecommunication interface detected the signal broadcast from the ID node.Such a sensed impact notification may also, in a further embodiment,indicate the detected impact force on the logistics container associatedwith the reporting container node was at least the threshold level ofimpact force. Thus, the received detection notification may includedetection details relating to the different monitored events (detectionof an electronic signal from a package ID node and detection of aphysical impact force) as well as level, timing, and thresholdinformation about such events centric to the container node's associatedlogistics container.

At step 5720, method 5700 proceeds with the managing node determining ifthe package is appropriately loaded within the logistics containerassociated with the reporting container node by comparing information inthe received detection notification from the reporting container nodeand anticipated inventory data for the logistics container associatedwith the reporting container node. In a more detailed embodiment ofmethod 5700, step 5720 may first involve having the managing nodeaccessing its memory storage to locate shipping information on therelevant package based upon the identification of the ID node includedin the detection notification. Then, the managing node may read theanticipated inventory data for the logistics container associated withthe reporting container node from the managing node's memory storage andverify the package is appropriately loaded based upon a comparison ofthe package's located shipping information and the anticipated inventorydata for the logistics container associated with the reporting containernode.

Next, at step 5725, method 5700 has the managing node transmitting anacknowledgement message to the reporting one of the container nodesbased upon whether the managing node determines the package isappropriately loaded. This feedback, in some further embodiments, may beused by the relevant container node (as explained above) as part ofgenerating and transmitting a misload message to a user access deviceoperated by logistics personnel (e.g., tablet or handheld smartphoneoperating as a type of ID node, such as user access devices 200, 205) sothat the logistics personnel are automatically and proactively notifiedof the misloading situation. This has an advantageous effect based uponthis technical interactive node solution of opening a corrective windowduring the loading operation, rather than finding out about themisloaded package after the logistics container has been closed up andmoved from the loading location.

Steps 5730 and 5735 of method 5700 may have the managing node updatedload operation related information in response to the receivedinformation from the reporting container node. In particular, at step5730, method 5700 has the managing node updating current inventoryinformation for the logistics container associated with the reportingcontainer node to reflect appropriate placement of the packageassociated with the ID node as being part of an inventory of contentsmaintained within the logistics container associated with the reportingcontainer node. For example, as shown in FIG. 55, master node 55110 mayupdate inventory data 55600 with current inventory information forlogistics container 55100A associated with container node 54000 a toreflect appropriate placement of package 55130 a (which is associatedwith ID node A 55120 a) as being part of what is now maintained withinlogistics container 55100A.

In some further detailed embodiments of method 5700, the acknowledgementmessage (originally transmitted back to the reporting container nodeabout whether the managing node determined the package is appropriatelyloaded in step 5725) may include a confirmation message to the reportingcontainer node with the updated current inventory information for thelogistics container associated with the reporting container node whenthe anticipated inventory data and the shipping information are used bythe managing node to verify that the package is appropriately loadedwithin the logistics container associated with the one of the containernodes. The confirmation message's updated current inventory informationmay, for example, reflect appropriate placement of the ID node's packageas being in the reporting container node's logistics container. Furtherstill, other embodiments may have the managing node reporting theupdated current inventory information up to the server in the wirelessnode network.

While step 5730 focuses on updating inventory information, step 5735 maybe employed in an embodiment of method 5700 to have the managing nodeupdate a loading productivity parameter in response to receiving thesensed impact notification. Such a loading productivity parameter isrelated to the logistics container associated with the particularreporting container node and indicates how quickly that logisticscontainer is being loaded as part of the loading operation. For example,master node 55110 may implement step 5735 in an embodiment of method5700 by updating productivity data 55605 as a way or recording relevantinformation about the loading process taking place relative to each ofthe containers 55100A-55100C that are monitored by container nodes 54000a-54000 c as well as master node 55110. Further still, and similar tothe updated current inventory information, an embodiment may also havemaster node 55110 reporting the updated loading productivity parameterto server 100 in the wireless node network. In other embodiments, suchupdated loading productivity parameter information may already be storedon the server 100 when the server operates as the managing node forpurposes of method 5700.

Finally, at step 5740, an embodiment of method 5700 may leverage barcodescan data that has been gathered relative to the package during loadingas a further check on whether the loading processes for the relevantlogistics container is being performed accurately. In more detail, atstep 5740, the managing node may compare (a) the sensed impactnotification indicating the package was loaded into the particularlogistics container associated with the reporting container node and (b)barcode scan data related to the package (such as scan data 55570reported to and stored within the managing node via the server or aseparate barcode scanner (e.g., barcode scanner ID node 55200) to verifythe accuracy of the barcode scan data.

In light of the above-described method 5700 focusing on specificoperations from a managing node perspective (and its variants), afurther exemplary system level embodiment involving motion-basedtracking of package placement within a logistics container may deploymultiple container node-enabled logistics containers (such as containers55100A-55100C), each of which are disposed and interact with a managingnode (such as master node 55110) as part of a monitored loadingoperation where one or more packages are being loaded into one or moreof the logistics containers. Each of the logistics containers has aninterior storage area capable of maintaining at least one package andincludes a respective container node that, as explained in theembodiments above relative to FIGS. 54-56, may monitor and track packageplacement within their logistics container. In this way, the differentlogistics containers in this system embodiment are respectivelyassociated with different container nodes.

In more detail, the container nodes in this system embodiment (such asthe examples shown in FIG. 55) represent a mid-level monitoring andmanaging element of a wireless node network. In general, each of thecontainer nodes in this exemplary system embodiment includes at least amotion sensor and two different communication interfaces. The containernode's motion sensor is deployed and disposed relative to the containernode's associated logistics container such that the motion sensor (withone or more sensing elements) operates to detect an impact force on thatlogistics container. In more detailed embodiments, the container node'smotion sensor may be implemented with an inertial sensor, a shockdetector, an accelerometer, and a microelectromechanical (MEMS) sensor.

One of the communication interfaces on the container node (e.g., shortrange communication interface 54480 on exemplary container node 54000 asshown in FIG. 54) operates to communicate over a short rangecommunication path with an ID node associated with a package to beshipped (such as ID node A 55120 a associated with package 55130 a or IDnode B 55120 b associated with package 55130 b). The ID node incommunication with the container node via this first communicationinterface is representative of a low-level element of the wireless nodenetwork. The other communications interface on the container node (e.g.,medium/long range communication interface 54485 on exemplary containernode 54000 as shown in FIG. 54) operates to communicate over a longrange communication path (typically in a distinct format when comparedto the format used by the first communication interface).

Configured in this manner, each of the container nodes in this systemembodiment are operative to cause the first communication interface toenter a scanning mode that electronically listens for a signal broadcastfrom such an ID node; identify a device signature of the ID node whenthe container node's first communication interface detects the signalbroadcast from the ID node; determine whether the container node'smotion sensor detected the impact force within a threshold time fromwhen the first communication interface detected the signal broadcastfrom the ID node, and then cause the container node's secondcommunication interface to transmit a notification to the managing node.Such a notification includes the identified device signature of the IDnode and motion status information reflecting whether the motion sensordetected the impact force within the threshold time.

The managing node in this exemplary system embodiment represents and isdisposed as an upper-level element of the wireless node network that islogically associated with each of the mid-level container nodes. Inother words, the managing node may be deployed in a server-authorizedlogical relationship with the container nodes that has the managing nodeinteractively receiving information from and managing each of thecontainer nodes. In more detail, the managing node in this systemembodiment (e.g., the master node 5510 as deployed in system 5500 shownin FIG. 55) communicates with each of the container nodes over the longrange communication path (e.g., Wi-Fi, cellular, or the like) to receivethe above-described transmitted notification from each of the containernodes. In response to receiving the transmitted notification from eachof the container nodes, the managing node in this system embodimentoperates at this upper-level of the network (e.g., a hierarchicalnetwork having the managing node, the container nodes on a level down,and one or more package ID node on a further level down) to identify oneof the container nodes. The managing node performs this identificationtask based upon the motion status information in the transmittednotification from the reporting container nodes indicates detection ofthe impact force. The managing node in this systems embodiment alsodetermines a confirmation level indicating a successful load of thepackage associated with the ID node (i.e., the ID node identified in thereceived notification). To do this, the managing node comparesinformation in the notification (e.g., the identified device signatureof the ID node derived from part of that node's broadcasted signal andmotion status information reflecting whether the motion sensor detectedthe impact force within the threshold time) and anticipated inventorydata for the logistics container associated with the identifiedcontainer node. In some embodiments, the motion status informationreflects whether the detected impact force was at least a thresholdlevel of force. Then, the managing node, as part of this exemplarysystem embodiment, transmits an acknowledgement message to theidentified one of the container nodes based upon the determinedconfirmation level.

In more detail, an embodiment of the managing node used as part of sucha system embodiment may deploy a memory storage maintaining at leastshipping information on the package and the anticipated inventory datafor the logistics container associated with the one of the containernode. The managing node may then, as part of the system, determine theconfirmation level indicating the successful load of the package byaccessing the memory storage within the managing node to locate theshipping information on the package based upon the identified devicesignature of the ID node included in the transmitted notification fromthe identified one of the container nodes. The managing node may alsoaccess its memory storage to locate the anticipated inventory data forthe logistics container associated with the identified one of thecontainer nodes. The managing node may then determine the confirmationlevel by comparing the shipping information on the package and theanticipated inventory data for the logistics container associated withthe identified one of the container nodes to verify the package wasproperly loaded.

Further still, if the confirmation level indicates the package wasproperly loaded, the system embodiment's managing node may updatecurrent inventory information maintained in the memory storage toreflect proper loading of the package associated with the ID node asbeing part of an inventory of contents maintained within the logisticscontainer associated with the identified one of the container nodes. Andif the confirmation level indicates the package was properly loaded, theacknowledgement message transmitted by the managing node may comprise aconfirmation message to the identified one of the container nodes. Sucha confirmation message may include the updated current inventoryinformation on the logistics container associated with the identifiedone of the container nodes. In further embodiments, the updated currentinventory information may be reported by the managing node to a serverat a top-level of the network (i.e., in a level above that of themanaging node, the container nodes, and any package associated ID nodesthat may make up the wireless node network)

However, if the confirmation level indicates the package was notproperly loaded, the acknowledgement message transmitted by the managingnode in the system embodiment may include an unload warning to theidentified one of the container nodes indicating a misloaded status ofthe package.

In addition to monitoring tracked package placement related to containernode-enabled logistics containers, the system embodiment's managing nodemay track productivity of loading the different logistics containers.For example, a further embodiment may have the managing node beingfurther operative to update a loading productivity parameter in responseto receiving the transmitted notification from one of the containernodes. Such a loading productivity parameter is related to the logisticscontainer associated with the identified one of the container nodestransmitting the notification, and indicates how quickly that particularlogistics container associated with the identified container node isbeing loaded as part of the monitored loading operation.

And as noted above, the managing node may verify the accuracy of barcodescan data gathered relative to the package during loading. To do so, afurther system embodiment may have the managing node verify the accuracyof barcode scan data captured during the monitored loading operation andmaintained within the memory storage by comparing (a) the confirmationlevel indicating the successful load of the package to (b) the barcodescan data related to the package.

While the above description relies on detecting an electronic signalbroadcast from a package's ID node as part of the multi-mode monitoringused to track package placement in the various embodiments described, afurther embodiment may use multi-mode monitoring in the form of impactdetection and barcode scanning (and in even some cases detecting ID nodesignals) in order to track package placement within a logisticscontainer using a container node. For example, as shown in FIG. 55,exemplary logistics container 55100A currently maintains differentpackages 55130 a-55130 c. Packages 55130 a and 55130 b are each enhancedwith respective ID nodes 55120 a and 55120 b. However, package 55130 cis not enhanced with an ID node. Thus, when package 55130 c is beingloaded, there are no ID node broadcast signals to detect emanating frompackage 55130 c. As such, a further embodiment of exemplary containernode 54000 a may still be able to track package placement withincontainer 55100A. In general, an impact detected by the container node'smotion sensor may be correlated back to information on a barcodescanning event for the same package as a way to track package placement.Thus, a package without an operating ID node may be loaded and receivedwithin logistics container 55100A with the exemplary container node54000 a deploying another type of multi-mode monitoring to track packageplacement pursuant to the method (and its variants) explained below withrespect to FIG. 58.

In more detail, FIG. 58 is a flow diagram illustrating an exemplarymotion-based method for improved tracking of package placement in acontainer node enabled logistics container in a monitored loadingoperation capable of handling ID node enabled packages and non-nodeenabled packages in accordance with an embodiment of the invention.Referring now to FIG. 58, exemplary method 5800 begins at step 5805where the container node monitors for a sensed impact force on thelogistics container using a motion sensor on the container node (such asmotion sensor 54465 on exemplary container node 54000 or any of sensorelements 54465 a-54465 c on exemplary container node 54000 a). As notedabove, an exemplary motion sensor may be implemented as an inertialsensor, a shock detector, an accelerometer, and a microelectromechanical(MEMS) sensor. In some embodiments, such as that shown in FIG. 55, themotion sensor may be implemented with multiple sensing elements that, infurther embodiments, are disposed proximate to different portions of aninterior storage area within the logistics container (e.g., sensorelements 54465 a-54465 c on exemplary container node 54000 a are showndisposed proximate different areas of floor 55205 of logistics container55100A).

At step 5810, method 5800 determines whether the container node's motionsensor has sensed an impact on the logistics container. For example, themotion sensor may report information on a level of the impact force assensed by one or more of the sensing elements within the interior of thelogistics container. If an impact force has been sensed, step 5810proceeds directly to step 5815. Otherwise, step 5810 proceeds back tostep 5805 for continued monitoring.

At step 5815, method 5800 proceeds with the container node transmittinga request for barcode information to a managing node. The requestedbarcode information corresponds to a barcode scanning event related tothe logistics container and captured within a threshold time prior towhen the impact force was sensed. In other words, the container noderequests barcode information from the managing node where the barcodeinformation is locally stored on the managing node (e.g., recentlystored information within scan data 55570 on master node 55110) asbarcode scan data captured related to loading the container node'slogistics container and captured sufficiently near when the containernode's motion detector sensed an impact force. For example, barcodescanner ID node 55200 may be located and used near a doorway intologistics container 55100A. As such, barcode scanner ID node 55200 maycapture and transmit relevant barcode information about package 55130 aup to master node 55110 as package 55130 a is being loaded intologistics container 55100A. In this way, master node 55110 may maintainsuch barcode information (including timing information about the barcodescanning event related to package 55130 a) as part of scan data 55570onboard the memory of master node 55110. As such, the container node atstep 5815 essentially queries the managing node (e.g., master node55110) for such relevant and time sensitive barcode information.Accordingly, at step 5820, if the container node receives the requestedbarcode information from the managing node, step 5820 proceeds to step5825. Otherwise, step 5820 proceeds back and remains waiting to receivethe requested barcode information.

In some embodiments, such relevant and time sensitive barcodeinformation may have already been transmitted to the container node bythe managing node or directly from an ID node based barcode scanner (asdescribed above) so that the time sensitive and relevant barcodeinformation is accessible on the container node without wastingprocessing time of the container node requesting and receiving suchinformation from an outside source (e.g., the managing node) in steps5815 and 5820.

At step 5825, method 5800 proceeds with the container node determiningif a first package is in the logistics container based upon the sensedimpact force and the received time sensitive barcode information. Inother words, the container node determines in step 5825 whether thebarcode information and the sensed impact force collectively indicatethat the package was placed within the interior storage area of thelogistics container by considering, for example, how quickly the impactforce was sensed after the scanned barcode event occurred. In someembodiments, the level of such a sensed impact force may also be afurther factor on whether the package was placed within the logisticscontainer (such as if the level of the sensed impact was too small orbelow a threshold level). In such an example where the sensed impact ismuch smaller than anticipated and less than a threshold, the package maynot be within that logistics container despite the timing of how quicklythe impact force was sensed relative to when the package's barcodeinformation was scanned. However, if the sensed impact is above thethreshold level and is sensed quickly after when the package's barcodeinformation was captured, then the package may be determined in step5825 to be within the logistics container. And even if the impact forcewas sensed as being above the threshold level, the time between suchimpact force sensing and when the package's barcode scan information iscaptured may be too long to determine that the package is in thelogistics container. Such differences in aspects of what is multi-modemonitored relative to the logistics container may be considered whendetermining if the package was placed within the logistics container.

Thus, if the container node determines the package was placed within thelogistics container as part of step 5825, then method 5800 proceeds fromstep 5825 to step 5830. Otherwise, method 5800 proceeds from step 5825directly back to step 5805 to monitor for other sensed impact forces andrestart the motion-based tracking of package placement within thelogistics container.

In a more detailed embodiment of method 5800, the determination in step5825 may be based upon a time difference between a time of captureassociated with the barcode scanning event and when the motion sensorsenses the impact force. As such, the determination in step 5825 maydepend upon whether this elapsed time or time difference is within athreshold time period. For example, an embodiment may use 5 seconds asan exemplary threshold time period to compare when there as a relevantbarcode scanning event for the logistics container to when an impactforce is detected relative to the logistics container. If the comparedor elapsed time is greater than 5 seconds, the container node determinesthe package was not placed within the logistics container. But if thecompared or elapsed time is less than 5 seconds, the container nodedetermines that such multi-modal monitoring results indicate the packagewas placed within the logistics container even if the package does nothave an ID node deployed within it to communicate with the containernode.

At step 5830, method 5800 may have the container node updating thecontainer node's inventory data. In particular, an embodiment of method5800 may have the container node updating inventory informationmaintained on a memory storage of the container node after determiningif this package is placed within the container based on the receivedbarcode information and the sensed impact force. For example, suchupdated inventory information may be kept as data 54600 stored withinmemory of exemplary container node 54000 as shown in FIG. 54.

At step 5835, method 5800 proceeds with the container node transmittinga notification to a managing node (such as a master node or a server inthe wireless node network). Such a notification reflects that thereceived barcode information and the sensed impact force collectivelyindicate the package was placed within the logistics container. In thisway, an embodiment of method 5800 may have the container node updating amanaging component higher within the network with a status of a loadingoperation as reflected by the local determination of the package havingbeen placed within the container node's logistics container even whenthe package is not enabled with an ID node.

At step 5840, an embodiment of method 5800 may have the container nodereceiving a confirmation message from the managing node in response totransmitting the notification at step 5835. Such a confirmation messagereceived in step 5840 verifies that the package was placed within thelogistics container. The verification in the confirmation message, insome instances, may confirm the package was placed in the appropriatelogistics container, after which the inventory information on the memorystorage may be updated (rather than at step 5830). However, in otherinstances, the verification in the confirmation message may indicatethis non-node enabled package has been misloaded or loaded into aninappropriate logistics container. Thus, an embodiment of method 5800may proceed to step 5850 from decision step 5845 if the package has beenmisloaded.

At step 5850, the container node associated with the logistics containernow may take proactive and automatic steps to rectify and address themisloaded package situation automatically detected. As such, thecontainer node in step 5850 may generate and transmit a misload messageto a user access device (UAD—such as user device 200 shown in FIG. 2)operating as a type of ID node and under the operation of loadingpersonnel involved in loading the logistics container related to thecontainer node. The container node, as part of step 5850, may alsorevise the inventory data locally stored indicating the current contentsof the logistics container. Thereafter, step 5850 proceeds back to step5805 to continue monitoring for detected or sensed impact forces on thelogistics container.

However, if the confirmation message received at step 5840 verifies thepackage was properly loaded and was supposed to be loaded into theparticular logistics container related to the container node performingmethod 5800, method 5800 need not engage in step 5850 and simplyproceeds from step 5845 directly back to step 5805 to continuemonitoring for detected or sensed impact forces on the logisticscontainer.

In a further embodiment, multi-mode monitoring by the container node forpackages with an ID node depending on detected electronic ID nodesignals and sensed impact forces (as set forth in the variousembodiments of method 5600 described above) may be combined withmulti-mode monitoring for packages without an ID node wheretime-sensitive barcode information is gathered and used with the sensedimpact forces (as set forth in the various embodiments of steps5805-5825) to supplement how to determine if a package is in theparticular logistics container. In other words, a first package thatdoes not have an ID node within it may be monitored by the containernode in compliance with method 5600 as described above (and itsvariants) while a second package that does have an ID node associatedwith it may also be monitored by the container node in compliance withmethod 5800 as described above (and its variants) as part of determiningwhether the first and second packages are placed within the containernode's logistics container.

In more detail, the embodiment of method 5800 as described above may befurther supplemented with steps that have the container node activatinga scanning mode of the container node to electronically listen for apackage ID node associated with a second package as the logisticscontainer is being loaded. In doing so, this further embodiment ofmethod 5800 may then have the container node detect a signal broadcastfrom the package ID node associated with the second package. This may beaccomplished, in some instances, when the container node detects aseries of increasingly stronger signals broadcast from the package IDnode that has the effect of indicating the second package is growingmore proximate to the logistics container. Next, this further embodimentof method 5800 may have the motion sensor on the container node sense afurther impact force on the logistics container after detecting thesignal broadcast from the package ID node.

The container node, in this further embodiment, may then determinewhether the detected signal broadcast from the package ID node and thesensed further impact force indicate that the second package was placedwithin the logistics container. For example, such a determination may bebased upon an elapsed time between when the container node detects thesignal broadcast from the package ID node with the second package andwhen the motion sensor senses the further impact force. In anotherexample, this determination may be based on whether such an elapsed timeis within a threshold time period. In still another example, thisdetermination may be based upon the further impact force as sensed bythe motion sensor (or multiple sensing elements collectively making upthe motion sensor) within an interior storage area of the logisticscontainer so that the sensed impact force is focused on and relevant tothe interior storage area.

This further embodiment of method 5800 may then have the container nodetransmitting a further notification to the managing node. Such a furthernotification reflects the detected signal (or series of signals) and thesensed further impact force collectively indicating that the secondpackage was placed within the logistics container.

Additionally, similar to steps 5640 and 5650 as described with respectto method 5600, this further embodiment of method 5800 may be extendedto also have the container node updating inventory informationmaintained on a memory storage of the container node after determiningwhether the detected signal broadcast from the package ID node and thesensed further impact force indicate the second package was placedwithin the logistics container, as well as receiving a confirmationmessage by the container node from the managing node, where theconfirmation message verifies that the second package was placed withinthe logistics container.

As described above relative to exemplary method 5800 and its variants,an exemplary container node performs such steps. Thus, exemplarycontainer node apparatus for improved tracking of package placement in alogistics container may implemented with an exemplary container node asshown in FIG. 54 (as container node 54000) and as described relative toFIG. 55 (as container node 54000 a) that is operative to function as setforth above in method 5800 and its variants.

Building upon such a container node apparatus, various systemembodiments may be used for improved tracking of package placementduring a monitored loading operation. For example, one system embodimentmay involve two components—i.e., the container node and its logisticscontainer. Such a container node may be implemented as described abovefor an exemplary container node apparatus (as shown in FIG. 54 (ascontainer node 54000) and as described relative to FIG. 55 (as containernode 54000 a) and operative to function as set forth above in method5800 and its variants). Likewise, the logistics container associatedwith the container node may be implemented as any of the exemplarylogistics containers discussed above, such as logistics container55100A.

Another system embodiment example may involve a master node (such asmaster node 55110) as it interacts and manages a container node asdescribed above relative to FIGS. 54, 55, 56, and 58 (and theirrespective variants). Such a system embodiment may be further expandedto include the logistics container associated with the container node,multiple container nodes (and their respective logistics containers),and a package ID node associated with one package (as a node-enabledpackage) and where there is another package being loaded that is notenabled with an ID node.

Active Shipment Management within a Node-Enabled Vehicle

As discussed above relative to FIGS. 20 and 21, embodiments that deploydifferent types of nodes described herein may be applied to a vehicularenvironment when dealing with logistics operations where a node is to belocated within a vehicle and, perhaps, relocated or removed (such aswhen delivering a node-enabled package from the vehicle). Beyond this,further embodiments may actively manage shipment of the node-enabledpackage from such a mobile delivery platform through interrelatedoperations and interactions between different types of nodes that verifythe package is on a particular vehicle and, in some embodiments, mayactively adjust the environment of the package (e.g., remotely control acooling/heating element associated with the package)). Still furtherembodiments may locate the container within the vehicle and considerweights/balance limitations and involved automated unloadinginstructions to address any issues automatically sensed and identified.

FIG. 59 is a diagram illustrating an exemplary active shipmentmanagement system as deployed within an exemplary wireless networkenabled vehicle in accordance with an embodiment of the invention.Referring now to FIG. 59, an exemplary active shipment management systemis shown in an embodiment with different types of nodes deployedrelative to an exemplary vehicle 59000. In general, similar to vehicle9300 shown in FIG. 20, exemplary vehicle 59000 is an example of ageneral mobile logistics transport or conveyance that can carry packagesor containers with packages. Such a vehicle may be implemented with anautomobile, a delivery van, an autonomous vehicle, a truck, a trailer, atrain car, an aircraft, a marine vessel (ship, barge), and the like.Within exemplary vehicle 59000, different containers or containerstorage units may be placed for transport, such as a cardboard box,metal or plastic container, ULD type of container, or other types ofstorage unit containers. Each of such containers (generally referred toas container storage units) within vehicle 59000 may maintain a varietyof different items and/or packages may be maintained. In other words,different embodiments of a storage unit container (such as storage unitcontainer A 59100A and storage unit container B 59100B) may store asingle package, multiple packages, unpackaged items, a mix of packagedand unpackaged items, or may storage a wide variety of different typesof packages that use different types of packaging materials (e.g.,corrugated fiberboard boxes, wooden and non-wooden pallets, containers,etc.) and in small or large numbers depending on the intended use andwhat is to be transported within such a storage unit container. As shownin FIG. 59, exemplary vehicle 59000 at least temporarily maintainsstorage unit container A 59100A and storage unit container B 59100B.Within storage unit container A 59100A, packages 59130 a-d are shown asbeing stored. Likewise, storage unit container B 59100B is illustratedas storing packages 59130 e-g.

Vehicle 59000 is illustrated as including a variety of node-baseddevices capable of communicating with each other as parts of a wirelessnode network, such as a package-based ID node, a container node, avehicle node, and a user access device (such as a smartphone or tablet)operating as a type of ID node. In particular, exemplary vehicle 59000includes a vehicle master node 59110 (a general example of a vehiclenode) disposed with the vehicle 59000. The vehicle master node 59110provides a wireless communication path from within the vehicle to amanaging node (such as facility master node 59114 or server 100) locatedexternal to the vehicle 59000. Each of storage unit container A 59100Aand storage unit container B 59100B within vehicle 59000 include arespective associated container node 59112 a, 59112 b. Container node59112 a communicates with and helps manage different ID nodes disposedwithin packages 59130 a-59130 c kept within storage unit container A59100A. Likewise, container node 59112 b communicates with and helpsmanage different ID nodes disposed within packages 59130 e-59130 g keptwithin storage unit container B 59100B. The ID nodes are associated withdifferent packages 59130 a-59130 g being shipped in different storageunit containers 59100A, 59100B within vehicle 59000. As generallyexplained above with reference to exemplary ID node 120 a (on which eachof the ID nodes in the various packages 59130 a-59130 g is based), eachof the ID nodes can send and receive advertising signals when disposedwithin the vehicle 59000 to communicate with other ID nodes as well aswith the container node associated with the storage unit containermaintaining the particular ID node.

As shown in FIG. 59, an embodiment of an exemplary active managementsystem relative to wireless network enabled vehicle 59000 has vehiclenode 59110 being operative to broadcast a management request within thevehicle 59000. The management request broadcast by vehicle node 59110relates to an ID node-enabled package being shipped (such as IDnode-enabled package 59130 a). In this example systems embodiment,exemplary container node 59112 a receives the broadcasted managementrequest related to the package 59130 a. Container node 59112 aidentifies the ID node associated with the package based upon shippinginformation included in the management request, and thus is able tofilter out signals from other ID nodes that are unrelated to themanagement request. With the identification of the ID node associatedwith the relevant package 59130 a, container node 59112 a listens withinits storage unit container A 59100A to receive one or more broadcastedadvertising signals from the package's ID node as part of determining alocation of that ID node (which may, for example, be accomplished viathe various techniques disclosed above). Based upon the determinedlocation of that ID node, the container node 59112 a verifies therelevant package is on vehicle 59000 and, in response to thelocation-based verification, transmits a verification message to thevehicle node 59110 indicating whether the package 59130 a is verified asbeing on the vehicle 59000.

In response to the verification message, vehicle node 59110 is furtheroperative to transmit a shipment update message to a managing nodeexternal to the vehicle (such as facility master node 59114 or server100 (directly or via an indirect path through network 105 when usingfacility master node 59114 as a messaging intermediary). Furthermore, inthis embodiment, those skilled in the art will appreciate that exemplaryfacility master node 59114 may be based upon exemplary master node 110 aas explained above relative to FIG. 4, and as deployed within FIG. 59may be associated with a delivery location, transfer facility, or amaster node associated with another type of delivery conveyance (e.g.,train, truck, ship, etc.) that manages or is able to communicate withvehicle node 59110 on vehicle 59000.

In this system embodiment, the shipment update message transmitted byvehicle node 59110 is based upon the verification message received bythe vehicle node 59110 and indicates updated shipping informationrelated to the package 59130 a. In more detail, the package's updatedshipping information may include a package status indicating the packageis or is not on the wireless network enabled vehicle 59000. In stillfurther embodiments, the package's updated shipping information receivedby vehicle node 59110 may include an unloading instruction for thepackage relative to the location of the ID node or an environmentalcondition information related to the package and the location of the IDnode (as explained in more detail below related to exemplary package59130 c).

In a further system embodiment, a container node may transmit warnings,generate specific instructions, and update logistics loading andunloading information relative to its storage unit container. Forexample, exemplary container node 59112 a may be further operative totransmit an imbalance warning to vehicle node 59110 when the containernode 59112 a identifies an imbalance condition based upon (a) shippinginformation related to package 59130 a and (b) a comparison of thedetermined location of the ID node for package 59130 a and aweight-related placement scheme, which may be related to vehicle 59000or the storage unit container 59100A associated with the container node59112 a. As such, the container node in this further system embodimentmay proactively and automatically identify an imbalance conditionrelative to the package as it sits within the storage unit containerand/or the vehicle as a whole and automatically notify the vehicle nodeabout such a condition. Thereafter, in this further system embodiment,the vehicle node may generate a vehicle imbalance notification inresponse to receiving the imbalance warning from the container node.Such a vehicle imbalance notification may be sent, for example, to anexternal managing node for the vehicle (e.g., facility master node 59114or server 100) or to an operator/occupant of the vehicle via anoperator's user access device 59200 (setup similarly as a user accessdevice (UAD) 200 operating as an ID node).

In another embodiment, the container node 59112 a, for example, maygenerate a location-based unload instruction for the package 59130 aupon verifying the package is on the vehicle 59000 and based upon thedetermined location of the ID node. The determined location upon whichthe location-based unload instruction is based may be the location ofthe ID node relative to within the particular storage unit container or,in other instances, relative to which the vehicle as a whole (or withina specific part of the vehicle, such as a cargo area).

In some embodiments, container node 59112 a may update a location-basedunload scheme for the vehicle 59000. This may happen locally to a copyof the location-based unload scheme for vehicle 59000 kept within thememory of container node 59112 a. In such a case, the container node59112 a modifies part of the information within its copy of thelocation-based vehicle unload scheme and may transmit the updated schemeto the vehicle node. However, in another example, container node 59112 amay not keep a local copy of the vehicle's location-based unload scheme.In such a case, the container node 59112 a may update a location-basedunload scheme for the vehicle 59000 by sending the modified informationto vehicle node 59110, which then modifies the vehicle node's copy ofthe location-based unload scheme.

In some active shipment management system embodiments, a storage unitcontainer or a package as part of the system may include an environmentcontrol unit (ECU) that essentially operates similar to a heater, airconditioner, and/or humidifier to keep a desired temperature and/orhumidity in its surrounding area for the benefit of what is beingshipped within the relevant storage unit container or package. FIG. 60is a diagram illustrating further details of an exemplary ID nodeenabled package maintained within the exemplary wireless network enabledvehicle as shown in FIG. 59 where the ID node enabled package includesan exemplary environmental control unit operative with the ID node inthe package in accordance with an embodiment of the invention. Referringnow to FIG. 60, exemplary storage unit container A 59100A from withinvehicle 59000 is shown in more detail with packages 59130 a-59130 d andtheir respectively associated ID nodes 59120 a-59120 d. As shown in FIG.60, items 60000 a-60000 d and package 59130 d (enabled with ID node59120 d) are collectively disposed in a nested configuration withinpackage 59130 c (enabled with ID node 59120 c). In this manner, package59130 c provides further packaging for groups of items and/or packages(some of which may be node-enabled, such as package 59130 d).

Package 59130 c is also illustrated having an exemplary environmentalcontrol unit (ECU) 60005 disposed within it and operatively coupled tothe ID node 59120 c associated with package 59130 c. ID node 59120 c isresponsive to a control message generated by container node 59112 a andprovided to ID node 59120 c in order to cause ID node 59120 c to adjusta setting of the environmental control unit 60005 by changing at leastone control parameter (e.g., temperature) in order to provide a desiredthermal effect on the contents of the ID node's package 59130 c. In afurther embodiment, container unit 59112 a may generate such a controlmessage based upon sensor data received from the package's ID node 59120c. For example, ID node 59120 c may include an environmental sensor60010 (similar to sensor 360 explained relative to an embodiment of IDnode 120 a in FIG. 3). Sensor 60010 operates to capture sensor datacharacterizing a status of package 59130 c, such as a temperature of theinterior of package 59130 c. Sensor 60010 provides the captured sensordata to ID node 59120 c, which may provide the sensor data to containernode 59112. As such, the control message generated by container node59112 may be an ECU adjustment based upon the sensor data as provided byID node 59120 c to the container node 59112 a.

Other embodiments may have ECU modules in more than one of the packagesor, more generally, in more than one of the storage unit containers.Furthermore, those skilled in the art will appreciate that a nested IDnode-enable package, such as package 59120 d, may indirectly providesensor data to a container node, such as container node 59112 a, using asensor associated with its ID node 59120 d to capture the sensor datacharacterizing the interior of package 59120 d. In this way, ID node59120 d may receive the sensor data from its sensor, transmit the sensordata to the ID node 59120 c for the enveloping package 59120 c, and thenID node 59120 c may provide the sensor data received from ID node 59120d back up to container node 59112 a as a type of feedback forcontrolling ECU 60005.

In light of the above-described exemplary components that make up andinteract with each other collectively as an exemplary active shipmentmanagement system, a further embodiment more specifically focuses onsystem's method of operation. In more detail, FIG. 61 is a flow diagramillustrating an exemplary method for active shipment management within awireless network enabled vehicle in accordance with an embodiment of theinvention. Referring now to FIG. 61, method 6100 begins at step 6105where a vehicle node (such as vehicle master node 59110) broadcasts amanagement request within a wireless network enabled vehicle (such asvehicle 59000). The management request broadcast by the vehicle node isrelated to a particular package being shipped.

At step 6110, method 6100 waits for a container node within the systemto receive the broadcasted management request. As such, if the containernode receives the broadcasted management request from vehicle's vehiclenode, then step 6110 proceeds to step 6115. Otherwise, method 6100 staysin step 6110. The receiving container node may be one of multiplecontainer nodes disposed within the wireless network enabled vehicle andis associated with a storage unit operative to maintain the package. Forexample, as shown in FIG. 59, at both of container nodes 59112 a and59112 b may have received the management request broadcast by vehiclemaster node 59110, and each of container node 59112 a and 59112 b areassociated with different storage unit containers that each may maintainthe package of interest related to the management request.

At step 6115, method 6100 proceeds with having the container nodeidentifying an ID node associated with the package of interest basedupon shipping information included in the management request. In thisway, for example, container node 59112 a may identify ID node 59120 aassociated with package 59130 a based upon shipping information for thepackage included in the management request received by container node59112 a.

At step 6120, method 6100 proceeds to have the container node verify thepackage is on the wireless network enabled vehicle based upon a locationof the ID node as determined by the container node. For example, as partof step 6120, container node 59112 a may interact with ID node 59120 ato determine the location (actionable or actual) of ID node 59120 a viavarious techniques as described above (e.g., methods that involvecontrolling an RF characteristic of a node (e.g., an RF output signallevel and/or RF receiver sensitivity level), determining relativeproximity, considering association information for ID node 59120 a,considering location adjustments for context information and an RFenvironment, chaining triangulation, as well as hierarchical andadaptive methods that combine various location methodologies to locateID node 59120 a). Such a location may be a relative location within thecontainer node's storage unit container or, in some cases, it may be alocation within the vehicle (or a portion of the vehicle).

At step 6125, an embodiment of method 6100 may determine whether thecontainer node has received any sensor data from the package. Asexplained above, a node-enabled package in an embodiment may alsoinclude an environmental control unit (ECU), which may be controlled bythe package's ID node to provide a desired thermal effect on thecontents of the package. For example, ID node 59120 c may provide sensordata from sensor 60010 in an embodiment of step 6125. As such, if thecontainer node has received sensor data from the package (notably, fromthe package's ID node), then step 6125 may proceed to steps 6130 and6135 in an embodiment of method 6100. Otherwise, step 6125 proceedsdirectly to step 6140.

At step 6130, an embodiment method 6100 proceeds with the container nodegenerating a control message for the located ID node. Such a controlmessage (which may be based upon the sensor data provided by the IDnode) adjusts an environmental control unit associated with the package,such as providing at least one control parameter to the located ID nodeto cause the environmental control unit to provide a desired thermaleffect on the package. And at step 6135, an embodiment of method 6100may also have the container node transmit the control message to the IDnode in order to effect the adjustment of the package's environmentalcontrol unit. For example, container node 59112 a as shown in FIG. 60may have received sensor data originally captured by sensor 60010 andtransmitted by ID node 59120 c. Such sensor data may indicate a risingtemperature above a desired threshold temperature (e.g., a desiredshipping temperature for items 60000 a-60000 d within package 59130 c).As a result, container node 59112 a may generate a control message thatchanges a temperature control parameter that causes ECU 60005 to beginto cool the interior of package 59130 c back down below or just to thedesired threshold temperature.

At step 6140, method 6100 proceeds with the container node transmittinga verification message to the vehicle node in response to the determinedof step 6120. Specifically, the verification message indicates whetherthe package is verified as being on the wireless network enabled vehicleas determined in step 6120. Thereafter, the vehicle node transmits ashipment update message to a managing node external to the wirelessnetwork enabled vehicle in step 6145. The managing node (e.g., a masternode (such as facility master node 59114) or a server (such as server100)) generally tracks and manages the vehicle node. Thus, the shipmentupdate message sent to the managing node is based upon the verificationmessage received by the vehicle node and indicating updated shippinginformation related to the package. For example, such updated shippinginformation may include an unloading instruction for the packagerelative to the location of the ID node, an environmental conditioninformation related to the package and the location of the ID node, apackage status indicating the package is on the wireless network enabledvehicle, and a package status indicating the package is not on thewireless network enabled vehicle.

A more detailed embodiment of method 6100 beyond step 6145 may have thecontainer node generating a location-based unload instruction for thepackage. Such a location-based unload instruction is based upon andrelated to the determined location of the ID node within the storageunit or within the vehicle.

Another detailed embodiment of method 6100 beyond step 6145 may have thecontainer node updating a location-based unload scheme for the wirelessenabled vehicle based upon the location of the ID node. As noted above,this may be accomplished by the container node modifying locally storeddata representing the location-based unload scheme for the vehicle or,in some embodiments, may have the container node sending modified dataor instructions on what to modify in data stored within the vehicle noderepresenting the location-based unload scheme.

FIG. 62 is a flow diagram illustrating still other steps in a furtherembodiment of the exemplary method 6100 for active shipment managementas shown in FIG. 61 in accordance with an embodiment of the inventionthat involves a weight-related placement scheme. Referring now to FIG.62, the additional steps (collectively referred to as sub-method 6200)begin at step 6205 where the container node may compare the determinedlocation of the ID node (from step 6120) to a weight-related placementscheme for the ID node's package. Such a weight-related placement schememay, for example, be related to the container node's storage unitcontainer or the vehicle (e.g., a storage area within the vehicle, suchas a van's rear storage area or an aircraft's cargo area).

At step 6210, the container node may access shipping information relatedto the particular package associated with the located ID node. Suchinformation may, in some embodiments, be locally already availablewithin memory of the container node. In other embodiments, the containernode may request and receive the particular shipping information fromthe vehicle node (which may have such information locally or need tofurther request and receive such information from a managing node, suchas facility master node 59114 or server 100).

At step 6215, the container node may automatically identify an imbalancecondition based upon the accessed shipping information related to thepackage and the resulting comparison of package's ID node locationrelative to the weight-related placement scheme. For example, theshipping information for the package may provide weight information forthis specific package to the container node. Thus, based upon thecontainer node's technical ability to locate the package's ID node andthe container node's determination of the package's weight (per theaccessed shipping information), the container node can automaticallyidentify an imbalance condition by comparing this information to theweight-related placement scheme without the need for a scale within thestorage unit container or the vehicle. If the imbalance condition isfound (e.g., comparing such information to the weight-related placementscheme shows an inconsistency with the scheme's threshold weightsrelative to particular parts of the storage unit container or vehicle),then step 6215 continues to steps 6220 and 6225. Otherwise, sub-method6200 concludes after step 6215 given such active shipment monitoringshows the package is placed in a location consistent with theweight-related placement scheme.

At step 6220, given the imbalance condition identified with respect tothe package, the container node may transmit an imbalance warning to thevehicle node so as to report the identified imbalance condition relatedto the package. At step 6225, sub-method 6200 may continue with thevehicle node generating a vehicle imbalance notification based upon theimbalance warning transmitted by the container node, and thentransmitting the vehicle imbalance notification to a managing node (suchas facility master node 59114 or server 100). In this manner, wirelessnode-based components within the node-enabled vehicle and external tothe node-enabled vehicle may be proactively informed about the imbalancecondition.

Further still, an embodiment may also have the vehicle node or managingnode automatically responding to such imbalance condition information(such as by sending a message to operator's user access device 59200that is operating as another wireless node). For example, the operator'suser access device 59200 may be implemented based upon an ID node with adisplay and such that the device can communicate directly with vehiclemaster node 59110 via a short range communication interface but thatcannot communicate directly with server 100. Such an implementation mayuse BLE formatted communications so as to keep the vehicle's operatorinformed of what is being automatically and proactively monitored andidentified onboard the vehicle. However, another example implementationof the operator's user access device 59200 may be based upon a type ofmaster node that can communicate directly with vehicle master node 59110via a short range communication interface (e.g., via a BLE formattedshort range communication path) and also communicate directly withserver 100 via a longer range communication interface (e.g., via Wi-Fior cellular communication paths)). Such an implementation may take theform of a cellular and Bluetooth enabled smartphone or portable tabletdevice having a touchscreen with which the operator may view informationand provide feedback to other wireless node components in the activeshipment management system.

In addition to the embodiments discussed above relative to FIGS. 59-62,an alternative embodiment of an active shipment management system withina wireless network enabled vehicle may involve ID nodes associated withrespective packages maintained within the vehicle and a vehicle nodedisposed within the vehicle (dispensing with the container node layerwithin the hierarchical wireless network of such a system). An exampleof such an alternative system embodiment is shown via the illustratedcomponents in FIG. 63 and the exemplary method steps as shown in FIGS.64 and 65, where interactive communications with the package ID nodesrest with the vehicle node and are not distributed at a container levelto storage container unit related container nodes.

In more detail, FIG. 63 is a diagram illustrating another exemplaryactive shipment management system embodiment as deployed within anexemplary wireless network enabled vehicle where the vehicle operates asa mobile storage unit for ID node enabled packages without usingseparate containers and related container nodes in accordance with anembodiment of the invention. In general, the system embodiment shown inFIG. 63 is similar to the embodiment shown in FIG. 59, with theexception being that there are no storage unit containers for thepackages 59130 a-59130 g and no container nodes. As such, each of thepackage ID nodes 59120 a-59120 g communicates directly with the vehiclenode 60110 and vice versa in a particular and unconventional manner aspart of such an embodiment of an active shipment management system.

In this illustrated embodiment in FIG. 63, the exemplary alternativesystem includes a vehicle node 60110 disposed within and associated withvehicle 60000. In more detail, such a vehicle 60000 may be implementedas a mobile storage unit capable of maintaining multiple shippableitems, such as a delivery van or an aircraft having a cargo area forhauling shippable items (e.g., packages). The vehicle node 60110,implemented as a type of master node (such as master node 110 a) andincludes at least a first communication interface providing a firstwireless communication path from within the vehicle 60000 to facilitymaster node 59114 operating as a managing node external to the vehicle.In some embodiments, the server may operate as the managing node for thevehicle master node 60110. Additionally, vehicle node 60110 alsoincludes a second communication interface providing a second wirelesscommunication path to ID nodes associated with packages 59130 a-59130 gbeing shipped within vehicle 60000. As such, the first wirelesscommunication path is distinct from the second wireless communicationpath so that the ID nodes may communicate directly with vehicle masternode 60110 but not directly with the managing node (e.g., server 100).Similar to that described relative to FIG. 59, each of the ID nodes inpackages 59130 a-59130 g can broadcast advertising signals when disposedwithin the vehicle 60000 as a way to communicate with the vehicle masternode 60110 and/or each other.

As part of this alternative system embodiment, the vehicle master node60110 is operatively programmed to perform a collective set of stepsthat, when considered together, provide for enhanced and unconventionalactive shipment monitoring and management relative to the vehicle 60000and its package contents. Specifically, as deployed in this alternativesystem embodiment, the vehicle master node 60110 operates to receive amanagement request over the first wireless communication path from themanaging node (whether implemented as the facility master node 59114 orthe server 100). Such a management request relates to a particularpackage being shipped, such as package 59130 c. In response to receivingthe management request, the vehicle master node 60110 identifies an IDnode associated with the package 59130 c based upon shipping informationincluded in the management request and then receives one or morebroadcasted advertising signals over the second wireless communicationpath from the ID node as part of determining a location of thatparticular ID node. Based upon the determined location of the ID node(as performed by the vehicle master node 60110), the vehicle master node60110 verifies that the package is on the vehicle 60000. Thereafter, thevehicle master node 60110 transmits a shipment update message over thefirst wireless communication path back up to the managing node (whetherthe facility master node 59114 or the server 100). Such a shipmentupdate message indicates whether the package is verified as being on thevehicle 60000 and indicates updated shipping information related to thepackage. Such updated shipping information may comprise, for example, anunloading instruction for the package 59130 c relative to the locationof its ID node, an environmental condition information related to thepackage 59130 c and the location of its ID node, a package statusindicating that package 59130 c is on the vehicle 60000, and a packagestatus indicating that package 59130 c is not on the vehicle (if that isin fact the case).

Similar to that shown in FIGS. 59 and 60, the alternative systemembodiment of FIG. 64 may also include an environment control unit (ECU)operatively coupled to an ID node and associated with a package. Forexample, package 59130 c is shown in FIG. 63 having an ECU that iscontrolled by the ID node within package 59130 c. In particular, anembodiment of the ECU may be controlled via a control message generatedby the vehicle node 60110 and provided to the ID node 59130 c to causethe ID node to adjust a setting of the ECU (e.g., a desired temperatureto which the ECU can be set). Similar to that shown in FIG. 60, the IDnode within package 59130 c of FIG. 63 may include a sensor (such as atemperature sensor) that captures sensor data (such as temperaturereadings) characterizing a status of the package 59130 c. Such sensordata may be provided by the ID node within package 59130 c to thevehicle node 60110, so that any control message generated by the vehiclenode 60110 may be based upon such sensor data. As such, the controlmessage generated by the vehicle node 60110 may provide one or morecontrol parameters to the located ID node, which then causes the ECU inaccordance with the provided control parameters to provide a desiredthermal effect on the package (e.g., heating or cooling the environmentwithin package 59130 c to a desired temperature consistent with theprovided control parameters).

Further embodiments of this alternative system may have the vehicle node60110 generating notifications or instructions relative to the locatedID node and its related package (such as package 59130 c). For example,vehicle node 60110 may generate a vehicle imbalance notification whenthe vehicle node 60110 identifies an imbalance condition when shippinginformation related to the package indicates a particular weight for thepackage and such a weight and location of the package (as correspondingto the determined location of the package's ID node) compared to aweight-related placement scheme automatically identify an imbalancecondition within the vehicle 60000. Such a weight-related placementscheme may be implemented as a data record accessible to the vehiclenode 60110 that relates to a balanced cargo load for the vehicle 60000.Such a data record representing such a weight-related placement schememay be loaded into vehicle node 60110 in a “push” type of manner fromthe managing node in communication with vehicle node 60110 (e.g.,facility master node 59114 or server 100). In this way, the vehicle node60110 may be preloaded with relevant placement, locating, and unloadinginformation specific to the particular contents to be carried withinvehicle 60000.

Still further embodiments of this alternative system may have vehiclenode 60110 updating a location-based unload scheme for the vehicle 60000stored as a data record within memory on vehicle node 60110 and/orgenerating a location-based unload instruction for the package 59130 cupon verifying the package is on the vehicle 60000 and based upon thedetermined location of the ID node within package 59130 c.

Thus, the above described alternative embodiment of an active shipmentmanagement system involves the particular operations of the vehicle node(such as vehicle master node 60110) as it interacts with at least one ofthe ID nodes (such as the ID node within package 59130 c) maintainedwithin the vehicle (such as vehicle 60000). Further system embodimentsmay also include, for example, multiple ID nodes, the managing node(such as facility master node 59114 and/or server 100), a nested packagehaving at least one further ID node enabled package within the nestedpackage, and/or an operator user access device (such as device 59200)that may be the recipient of notifications and instructions from thevehicle node regarding the located ID node within the vehicle.

As noted above, FIGS. 64 and 65 provide exemplary steps on how such avehicle node (e.g., vehicle master node 60110) in such an alternativesystem embodiment for active shipment management may operate. Inparticular, FIG. 64 is a flow diagram illustrating an exemplary methodfor active shipment management within a wireless network enabled vehicleas shown in FIG. 63 in accordance with an embodiment of the invention.Referring now to FIG. 64, exemplary method 6400 begins at step 6405where a managing node (such as facility master node 59114 or server 100)broadcasts a management request to a vehicle node within a wirelessnetwork enabled vehicle (such as node 60110 within vehicle 60000). Themanagement request broadcast by the managing node is related to aparticular package being shipped.

At step 6410, method 6400 waits for a vehicle node within the system toreceive the broadcasted management request. As such, if the vehicle nodereceives the broadcasted management request from managing node, thenstep 6410 proceeds to step 6415. Otherwise, method 6400 stays in step6410. The vehicle associated with the vehicle node may be implemented asa type of mobile storage unit that can at least temporarily maintainmultiple shipping items (such as a delivery van that can temporarilystore multiple packages for delivery or an aircraft that can temporarilystore multiple packages for transport).

At step 6415, method 6100 proceeds with having the vehicle nodeidentifying an ID node associated with the package of interest basedupon shipping information included in the management request. In thisway, for example, vehicle node 60110 may identify the ID node associatedwith package 59130 a based upon shipping information for the packageincluded in the management request received by vehicle node 60110 fromthe managing node.

At step 6420, method 6400 proceeds to have the vehicle node verify thepackage is on the wireless network enabled vehicle based upon a locationof the package's ID node as determined by the vehicle node. For example,as part of step 6420, vehicle node 60110 may interact with the ID nodeassociated with and packed within package 59130 c to determine thelocation (actionable or actual) of that ID node via various techniquesas described above (e.g., methods that involve controlling an RFcharacteristic of a node (e.g., an RF output signal level and/or RFreceiver sensitivity level), determining relative proximity, consideringassociation information for ID node 59120 a, considering locationadjustments for context information and an RF environment, chainingtriangulation, as well as hierarchical and adaptive methods that combinevarious location methodologies to locate the ID node within package59120 c). Such a location may, for example, be determined as a locationwithin the mobile storage unit implemented by the vehicle.

At step 6425, an embodiment of method 6400 may determine whether thevehicle node has received any sensor data from the package. As explainedabove, a node-enabled package in an embodiment may also include anenvironmental control unit (ECU), which may be controlled by thepackage's ID node to provide a desired thermal effect on the contents ofthe package. For example, the ID node within package 59130 c may providesensor data from the ID node's sensor in an embodiment of step 6425. Assuch, if the vehicle node has received sensor data from the package(notably, from the package's ID node), then step 6425 may proceed tosteps 6430 and 6435 in an embodiment of method 6400. Otherwise, step6425 proceeds directly to step 6440.

At step 6430, an embodiment method 6400 proceeds with the vehicle nodegenerating a control message for the located ID node. Such a controlmessage (which may be based upon the sensor data provided by the IDnode) adjusts an environmental control unit associated with the package,such as providing at least one control parameter to the located ID nodeto cause the environmental control unit to provide a desired thermaleffect on the package. And at step 6435, an embodiment of method 6400may also have the vehicle node transmit the control message to the IDnode in order to effect the adjustment of the package's environmentalcontrol unit. For example, vehicle node 60110 as shown in FIG. 63 mayhave received sensor data originally captured by the sensor in the IDnode associated with package 59130 c. Such sensor data may indicate arising temperature above a desired threshold temperature (e.g., adesired shipping temperature for the contents of package 59130 c). As aresult, vehicle node 60110 may generate a control message that changes atemperature control parameter that causes the ECU in package 59130 c tobegin to cool the interior of package 59130 c back down below or just tothe desired threshold temperature.

At step 6440, method 6400 proceeds with the vehicle node transmitting ashipment update message to a managing node external to the wirelessnetwork enabled vehicle. The managing node (e.g., a master node (such asfacility master node 59114) or a server (such as server 100)) generallytracks and manages the vehicle node 60110. The transmitted shipmentupdate message is the way the vehicle node indicates whether the packageis verified as being on the wireless network enabled vehicle and alsoindicates updated shipping information related to the package. Andsimilar to what has been described, such updated shipping informationmay include an unloading instruction for the package relative to thelocation of the ID node, an environmental condition information relatedto the package and the location of the ID node, a package statusindicating the package is on the vehicle, and a package statusindicating the package is not on the wireless network enabled vehicle.

A more detailed embodiment of method 6400 beyond step 6440 may have thevehicle node generating a location-based unload instruction for thepackage. Such a location-based unload instruction is based upon andrelated to the determined location of the ID node within the vehicle.

Another detailed embodiment of method 6400 beyond step 6440 may have thevehicle node updating a location-based unload scheme for the wirelessenabled vehicle based upon the location of the ID node. As noted above,this may be accomplished by the vehicle node modifying locally storeddata representing the location-based unload scheme for the vehicle.

FIG. 65 is a flow diagram illustrating still other steps in a furtherembodiment of the exemplary method 6400 for active shipment managementas shown in FIG. 64 in accordance with an embodiment of the inventionthat involves a weight-related placement scheme. Referring now to FIG.65, the additional steps (collectively referred to as sub-method 6500)begin at step 6505 where the vehicle node may compare the determinedlocation of the ID node (from step 6420) to a weight-related placementscheme for the ID node's package. Such a weight-related placement schememay, for example, be related to the mobile storage area within thevehicle (e.g., such as a van's rear storage area or an aircraft's cargoarea).

At step 6510, the vehicle node may access shipping information relatedto the particular package associated with the located ID node. Suchinformation may, in some embodiments, be locally already availablewithin memory of the vehicle node. In other embodiments, the vehiclenode may request and receive the particular shipping information fromthe managing node (which may have such information locally or need tofurther request and receive such information from a server, such asserver 100).

At step 6515, the vehicle node may automatically identify an imbalancecondition based upon the accessed shipping information related to thepackage and the resulting comparison of package's ID node locationrelative to the weight-related placement scheme. For example, theshipping information for the package may provide weight information forthis specific package to the vehicle node. Thus, based upon the vehiclenode's technical ability to interact with the package's ID node anddetermine a location of the package's ID node and the vehicle node'sdetermination of the package's weight (per the accessed shippinginformation), the vehicle node can automatically identify an imbalancecondition by comparing this information to the weight-related placementscheme without the need for a scale within the vehicle. If the imbalancecondition is found (e.g., comparing such information to theweight-related placement scheme shows an inconsistency with the scheme'sthreshold weights relative to particular parts of the vehicle), thenstep 6515 continues to step 6520. Otherwise, sub-method 6500 concludesafter step 6515 given such active shipment monitoring shows the packageis placed in a location consistent with the vehicle's weight-relatedplacement scheme.

At step 6520, sub-method 6500 may continue with the vehicle nodegenerating and transmitting a vehicle imbalance notification to amanaging node (such as facility master node 59114 or server 100). Inthis manner, wireless node-based components within the node-enabledvehicle and external to the node-enabled vehicle may be proactivelyinformed about the vehicle's imbalance condition.

Further still, an embodiment may also have the managing nodeautomatically responding to such imbalance condition information (suchas by sending a message to operator's user access device 59200 that isoperating as another wireless node). For example, the operator's useraccess device 59200 shown in FIG. 63 (similar to that shown in FIG. 59)may be implemented based upon an ID node with a display and such thatthe device can communicate directly with vehicle master node 60110 via ashort range communication interface but that cannot communicate directlywith server 100. Such an implementation may use BLE formattedcommunications so as to keep the vehicle's operator informed of what isbeing automatically and proactively monitored and identified onboard thevehicle. However, another example implementation of the operator's useraccess device 59200 may be based upon a type of master node that cancommunicate directly with vehicle master node 60110 via a short rangecommunication interface (e.g., via a BLE formatted short rangecommunication path) and also communicate directly with server 100 via alonger range communication interface (e.g., via Wi-Fi or cellularcommunication paths)). Such an implementation may take the form of acellular and Bluetooth enabled smartphone or portable tablet devicehaving a touchscreen with which the operator may view information andprovide feedback to other wireless node components in the activeshipment management system.

Deployment of Enhanced Multi-Radio Features in Nodes

Further embodiments may leverage the use a specially enhanced containernode within a logistics container in order to better localize othernodes within the container, outside the container, and/or supported on apart of the container. In general, such enhanced embodiments may involvemultiple radio elements (e.g., multiple antenna elements, dedicatedradio units, or both) deployed as part of the container node to monitorinside, outside, or both inside and outside of the logistics container.This may be applied with logistics containers that are sealed containersthat transport packages or items for shipment (such as with a ULD, aclosed trailer, train car, or intermodal shipping container) but mayalso be used with logistics containers based upon a storage platform(such as an enhanced base pallet that is used to support packages beingshipped or an open trailer having a floor and side walls that supportspackages being shipped). Different antenna configurations may be used tofurther enhance node locating via focused antenna patterns (e.g.,directional vs. omni-directional vs. phased array). Additionalembodiments may have the container node's controller (e.g., theprogrammed processing unit within the container node) actively manageand select which radio/antenna elements to use, thus providing morerefined location information of packages within the container and/orproviding location/orientation information about the container asdisposed within a physical storage (e.g., a building, a vehicle, anaircraft, a trailer, and the like). Such information as generated by thecontainer node at that level allows for a multiple antenna node-basedsolution that yields measurement-based information used, for example, aspart of automatic weight and balance determinations for the containernode's logistics container.

FIG. 66 is a diagram illustrating an exemplary enhanced container nodeapparatus disposed as part of a wireless node network capable logisticscontainer and having at least one improved radio transceiver forreception of a node inside of the logistics container as deployed inaccordance with an embodiment of the invention. Referring now to FIG.66, exemplary logistics container 66100A is shown maintaining twopackages 66130 a, 66130 b. Package 66130 a is enabled with ID node A66120 a. Likewise, package 66130 b is enabled with ID node B 66120 b. Anexemplary enhanced container node 66000 is disposed on the logisticscontainer 66100A to generally monitor the interior of container 66100Aas well as communicate with a facility master node 110 a associated witha physical storage (such as a vehicle or building). Facility master node110 a may be implemented as a type of wireless master node element thatcan communicate with one or more container nodes (such as container node66000) as well as electronically interact with server 100 (via network105).

Exemplary enhanced container node 66000 may be implemented similar tocontainer nodes 38000, 41000, or 54000 a as described above but withdifferences related to how they respectively implement theircommunication interfaces and the respective programming of theirprocessing units. In more detail, exemplary enhanced container node66000 is shown having a processing-based controller module 66005 that isoperatively coupled to each of two different radio transceivers (RTxunit 66480 and RTx 66485) for communicating with nodes within thelogistics container and with nodes external to the logistics containeras explained in more detail below. In general, controller module 66005is a processor-based electronic computing circuit, such as amicrocontroller, that contains a processing core, memory (volatile andnon-volatile memory), and programmable input/output peripherals (e.g.,UARTs, timers, counters, clocks, A/D and D/A converters, buffers, serialinterfaces, parallel interfaces, sensors, and the like). Someembodiments of controller module 66005 may be implemented as a singleintegrated circuit (e.g., system on a chip (SOC) type devices) whileother embodiments may implement the container node's controller modulewith a collection of separate circuit devices, such as a processingunit, memory, processing peripherals, and programmable interfaces asneeded for the intended container node implementation. The memory withinthe controller module 66005 is operative to maintain relevantoperational data and program instructions to support the operations asdescribed in more detail below when using such radio transceivers.

While the exemplary short range and medium/long range communicationinterfaces as described with respect to exemplary container nodes 38000,41000, or 54000 a allow for the use of separate communication paths whencommunicating with different nodes, the use of further enhanced radiotransceivers RTx unit 66480 and RTx 66485 allows the container node66000 to refine and improve how it can communicate with and locate othernodes. As shown in FIG. 66, RTx unit 66485 is generally a radiotransceiver operatively coupled to the container node controller 66005that includes an antenna 66500. As such, RTx unit 66485 facilitateswireless communication access through antenna 66500 to the facilitymaster node 110 a disposed external to the logistics container 66100A.However, in the embodiment shown in FIG. 66, RTx unit 66480 is generallyanother radio transceiver operatively coupled to the container nodecontroller 66005 that includes multiple antenna elements 66505 a-66505d. Collectively, these antenna elements 66505 a-66505 d are disposed ina spatially disperse configuration relative to the logistics container66100A and provide RTx unit 66480 with multi-antenna wirelesscommunication access to one or more package ID nodes (e.g., ID node A66120 a and/or ID node B 66120 b) disposed within the logisticscontainer 66100A.

In such a spatially disperse configuration, the antenna elements 66505a-66505 d are physically located relative to different parts of thelogistics container 66100A. For example, in one embodiment, the antennaelements 66505 a-66505 d may be disposed along an axis of the logisticscontainer, such as on the interior ceiling of the logistics containeralong a central axis that runs the length of the logistics container. Assuch, each of the antenna elements 66505 a-66505 d may be implementedwith an antenna pattern focused on one of multiple different portions ofa storage area within the logistics container 66100A, which furtherhelps to localize signals monitored within the storage area. In moredetail, an embodiment may have these antenna elements 66505 a-66505 dmounted, secured, attached, or otherwise disposed on multiple differentinterior surfaces (such as along the ceiling, door, side walls, orfloor) of the logistics container 66100A. As such, an embodiment ofcontainer node 66000 may deploy antenna elements 66505 a-66505 d in aspatially disperse configuration that allow for the RTx unit 66480 touse such elements as parts of a collective beamforming phased arrayantenna where signals received from different antenna elements areprocessed by RTx unit 66480 for adaptive and directional signaltransmission and reception relative to the interior of the logisticscontainer 66100A (rather than a simple omni-directional approach using asingle antenna element).

FIGS. 67 and 68 provide further details with respect to how exemplaryRTX unit 66480 may be implemented in different embodiments. Inparticular, FIG. 67 is a diagram of further internal details ofexemplary enhanced container node having a radio transceiver withdedicated radio units and corresponding antenna elements in accordancewith an embodiment of the invention. Referring now to FIG. 67, exemplaryradio transceiver unit RTx 67480 is coupled to container node controllermodule 66005 and includes a central interface 67000, multiple dedicatedradio units 67005 a-67005 d, and multiple antenna elements 66505 a-66505d that each correspond to one of the dedicated radio units 67005 a-67005d. Central interface 67000 may be implemented with switching circuitrythat can provide signals and commands from controller module 66005 toselective ones of the dedicated radio units 67005 a-67005 d. Each of thededicated radio units 67005 a-67005 d generally has its own radiotransceiver for independent reception and transmission of wirelesssignals through a corresponding one of the antenna elements 66505a-66505 d. Those skilled in the art will appreciate that in this manner,each of the dedicated radio units may be individually selected (e.g.,via commands from controller module 66005 and the switching circuitry ofcentral interface 67000) to receive or transmit information but withthis architecture can also do so simultaneously while other dedicatedradio units receive or transmit wireless signals (or at least haveoverlapping signals being received or transmitted to other nodes).

FIG. 68 is a diagram of further internal details of an exemplaryenhanced container node having an alternative type of radio transceiverunit capable of working with multiple antenna elements. Referring now toFIG. 68, exemplary container node 66000 is shown with RTx unit 68480operatively coupled to the container node's controller module 66005 andincludes a single central radio unit 68000 that is coupled to themultiple antenna elements 66505 a-66505 d via switching circuitry 68005(generally labeled “mux” corresponding to multiplexer). Mux 68005 may beimplemented with switching circuitry that can provide a selectivecommunication path from an RF input/output of central radio unit 68000to and from antenna elements 66505 a-66505 d. As such, those skilled inthe art will appreciate that each of the antenna elements 66505 a-66505d may be individually selected or selected in subgroups (e.g., viacommands from controller module 66005 that have central radio unit 68000controlling the switching circuitry of mux 68005) so that the centralradio unit 68000 can receive or transmit information via the selectedelement or subgroup of antenna elements, but does so with a single radiounit (rather than multiple radio units as shown in FIG. 67).

As such, an apparatus embodiment may use elements of such an enhancedcontainer node 66000 as part of a wireless node network capablelogistics container. In more detail, such an apparatus embodiment wouldinclude at least a container node controller and two different radiotransceivers. The container node controller, such as controller module66005 as shown in FIGS. 66-68, is an element of the container node thatis disposed on the logistics container. One of the radio transceivers inthis apparatus embodiment (e.g., RTx unit 66485) is operatively coupledto the container node controller and has an antenna (e.g., antennaelement 66500) providing this radio transceiver with wirelesscommunication access to a master node (e.g., facility master node 110 a)disposed external to the logistics container. The second of the radiotransceivers (e.g., RTx unit 66480) is also operatively coupled to thecontainer node controller and includes multiple antenna elements (e.g.,antenna elements 66505 a-66505 d) disposed in a spatially disperseconfiguration relative to the logistics container (such as along an axisof the logistics container, on different surfaces of the logisticscontainer, or near different corners of the logistics container). Thesemultiple antenna elements advantageously provide the second radiotransceiver with multi-antenna wireless communication access to an IDnode within a package (e.g., ID node A 66120 a within package 66130 a)disposed within the logistics container.

An embodiment of the second radio transceiver may be implemented with asingle central radio unit (such as that shown in FIG. 68) that iscoupled to each of the antenna elements. However, another embodiment ofthe second radio transceiver may be implemented with multiple radiounits where each are respectively coupled with different antennaelements. In more detail, the second radio transceiver may beimplemented to have a central communication interface operativelycoupled to the container node controller, and with each of the multiplededicated radio units coupled to the central communication interface andone of the antenna elements. In this way, the particular antenna elementcoupled to each of the dedicated radio units may monitor a differentportion of the logistics container's storage area. For example, as shownin FIGS. 66 and 67, each of dedicated radio units 67005 a-67005 d areconnected with respective ones of antenna elements 66505 a-66505 d,which are spatially dispersed to monitor different portions of theinterior of logistics container 66100A.

In operation, the container node controller of this apparatus embodimentmay send a location control message to the second radio transceiver whenattempting to locate the package ID node. As such, the second radiotransceiver responds by selecting different subsets of the antennaelements to receive an inbound wireless signal from the package ID node.In doing so, the second radio transceiver detects reception informationabout the inbound wireless signal for each of the different selectedsubsets of the antenna elements as they are selected. Such detectedreception information (e.g., different signal power levels of thebroadcast advertising signals from the package ID node as received bythe different subsets of antenna elements) is collectively provided bythe second radio transceiver to the container node controller. This mayhappen in a burst with all of the different detected receptioninformation or may happen sequentially as each different subset ofantenna elements are selected and corresponding signal receptioninformation is detected.

With the detected reception information from the second radiotransceiver, the container node controller determines a location of thepackage ID node relative to the logistics container based upon thedetected reception information from the second radio transceiver. Forexample, the container node controller may find that the signal powerlevel of package ID node signals detected are strongest relative tocertain antenna elements located relative to certain parts of thelogistics container. As such, the container node controller maydetermine a localized relative position of the package ID node usingsuch reception information leveraged by the different subsets of antennaelements of the second radio transceiver. Thereafter, the container nodecontroller may send an instruction to the first radio transceiver tocause the first radio transceiver to transmit a location determinationmessage to the master node. Such a location determination messagereflects the determined location of the package ID node relative to thelogistics container.

In a further apparatus embodiment, the second radio transceiver may beoperative to select the different subsets of antenna elements by thesecond radio transceiver may be accomplished when the second radiotransceiver controls which of the different subsets of the antennaelements provides a wireless reception input for the second radiotransceiver. For example, with the antenna elements disposed in aspatially diverse configuration (such as on an axis of the containeralong the ceiling of the container), the second radio transceiver maycycle through each antenna element being connected to the wirelessreception input of the transceiver so that as each antenna element isconnected, the second radio transceiver is using an antenna having areception field in different parts of the logistics container. And asthe second radio transceiver cycles through different subsets of theantenna elements (e.g., individually through each element, throughdifferent groups of the antenna elements, such as a group of the antennaelements on one side of the container and another group of the antennaelements disposed on another side of the container), the second radiotransceiver can detect a different observed signal strength of theinbound wireless signal for each of the different selected subsets ofthe antenna elements.

Using such detected signal strengths relative to the different selectedsubsets of the antenna elements, the location of the package ID noderelative to the logistics container may be determined as a relativelocation within the storage area of the logistics container. Morespecifically, an embodiment may have the container node controllerdetermine the relative location of the package ID node within thestorage area of the logistics container in response to receivingdetected reception information from the second radio transceiver by (a)comparing the detected reception information for each of the differentselected subsets of the antenna elements; (b) identifying one of theselected subsets of antenna elements having a maximum observed signalstrength of the inbound wireless signal; and (c) determining therelative location of the package ID node as being related to a focalarea within the storage area for the identified one of the selectedsubsets of antenna elements in (b). In other words, by deployingmultiple antenna elements in a physically and spatially disperseconfiguration, one of the antenna elements may observe the package IDnode's signals to be higher than the other antenna elements, which thenhas the container node's controller determining that the package IDnode's relative location is the location within the container's storagearea where that one antenna element's is focused.

In still additional apparatus embodiments, the container node controllermay generate placement feedback information about the package ID nodebased upon the determined location of the package ID node relative tothe logistics container. In such a case, the container node controllermay also cause the first radio transceiver to broadcast a placementfeedback message to the master node based upon the generated placementfeedback information. The container node controller may generate suchplacement feedback information as including a loading status parameter,a current weight parameter, and/or a current balance parameter. Theloading status parameter may indicate whether the package ID node islocated within the logistics container in accordance with a loading planfor that logistics container compared to the determined location of thepackage ID node relative to the logistics container. The current weightparameter for the logistics container may be based at least upon aweight of a package associated with the package ID node. And the currentbalance parameter for the logistics container may be based at least uponthe determined location of the package ID node relative to the logisticscontainer and the weight of the package associated with the package IDnode. Thus, an embodiment of the container node controller may evenfurther enhance monitored loading/shipment/unloading operations withsuch automatic and proactive messaging about placement feedback in timeto avoid placement, weight, and balance related issues with the IDnode's package as it sits within the logistics container.

In the above described enhanced container node apparatus embodiment,such an apparatus may be used with various types of logisticscontainers. For example, the enhanced container node apparatus may beused with a unit load device (ULD) container capable of beingtransported within an airplane; a trailer capable of being moved by avehicle (such as a cargo trailer pulled by a truck); a train car capableof being moved on a railway system; and an intermodal shipping containercapable of being moved on at least two different types of transportationmodalities.

As described above relative to FIGS. 44-53, an exemplary logisticscontainer may also be implemented using a logistics storage platform,such as a palletized base platform, that supports items (e.g., ID nodeenabled packages) that are being stored, moved or transported. In moredetail, this type of exemplary logistics container may be implementedwith a base platform and a flexible cover that is removably attachableto the base platform in order to secure the package ID node relative tothe base platform.

Another exemplary logistics container may be implemented using one ormore shelves capable of supporting items (e.g., ID node enabledpackages). Each of such shelves may be associated with an enhancedcontainer node deployed with multiple antenna elements to communicatewith the package ID nodes supported on the shelf in a more localizedmanner as described above.

While the above description relates to an exemplary enhanced containernode apparatus, such an apparatus may be deployed as part of a largersystem embodiment that includes the logistics container. In someexamples of such a system embodiment, some or all of the elements makingup such an enhanced container node may be built into or be an integratedpart of the logistics container. However, in other examples, thecontainer node with its multiple antenna elements may be disposed on thelogistics container when operating as the system but in a configurationthat has the container node being removable and replaceable and/or withantenna elements that may be changed in configuration to adaptivelymonitor different portions of the container's storage area as desired ordictated by the packaging contents intended to be shipped within thecontainer.

In more detail, an exemplary embodiment of an enhanced wireless nodenetwork capable container system, such as that shown in FIG. 66,generally includes a logistics container, a container node controller,and two different radio transceivers—one of which having multipleantenna elements. The system's container node controller (such ascontroller module 66005) is disposed on the logistics container—e.g., inan attached or integrated manner relative to an accessible storage areawithin the logistics container or in a removable manner using anattachable housing for the container node within which the containernode controller is disposed. The system's first radio transceiver (e.g.,RTx unit 66485) is operatively coupled to the container node controllerand has a first antenna (e.g., 66500) providing wireless communicationaccess to a master node (e.g., facility master node 110 a) disposedexternal to the logistics container. While the system's second radiotransceiver (e.g., RTx unit 66480) is also operatively coupled to thecontainer node controller, the second radio transceiver advantageouslyincludes multiple antenna elements (e.g., antenna elements 66505 a-66505d) placed in a dispersed configuration relative to the logisticscontainer so as to provide reception/transmission coverage that isspread out within different parts of the logistics container. As such,the antenna elements provide the second radio transceiver withmulti-antenna wireless communication access to a package ID nodedisposed with a package maintained within the logistics container. Forexample, antenna elements 66505 a-66505 d are disposed in differentparts of logistics container 66100A to provide RTx unit 66480 ofcontainer node 66000 with multi-antenna wireless localized access to theID node A 66120 a within package 66130 a.

In this configuration, the system's container node and the second radiotransceiver interact in an unconventional manner to determine thelocation of the package ID node within the container. In more detail,the system's container node controller may generate and send a locationcontrol message to the system's second radio transceiver when attemptingto determine the location of the package ID node within the container.In response, the second radio transceiver selects different subsets ofthe antenna elements to receive an inbound wireless signal from thepackage ID node so that the second radio transceiver detects receptioninformation about the inbound wireless signal for each of the differentselected subsets of the antenna elements. In more detail, the secondradio transceiver may perform this type of selection and detection bycontrolling which of the different subsets of the antenna elements(located in different parts of the logistics container) provides awireless reception input for the second radio transceiver. For example,as shown in FIG. 66, antenna elements 66505 a-66505 d are disposedrelative to 4 different parts of logistics container 66100A. ExemplaryRTx unit 66480 may select each of these antenna elements as a subset ofthe group of antenna elements and selectively connect each of theantenna elements to an RF front end of RTx unit 66480. Depending on howthe RTx unit 66480 is implemented, this may involve selecting aparticular dedicated radio unit within RTx unit 66480 for a particularantenna element via a central communication interface (such as thatshown in the radio transceiver embodiment of FIG. 67) or it may involveestablishing a switched electrical connection between a single centralradio unit within RTx unit 66480 and the particular antenna element(such as that shown in the radio transceiver embodiment of FIG. 68).Thus, as each of the antenna elements 66505 a-66505 d are connected tothe RF front end of RTx unit 66480, an embodiment may have the RTx unit66480 observing a signal strength of the detected inbound wirelesssignal that is being broadcast from package ID node A 66120 a. This maybe done for each of the different subsets of antenna elements (e.g., aseach antenna element is connected to and provides a reception front endantenna for RTx unit 66480).

The system's second radio transceiver provides the detected receptioninformation to the container node controller. In general, the secondradio transceiver may provide the detected reception information (e.g.,the observed signal strengths relative to each selected subset ofantenna elements) to the container node controller in a single messageafter all the reception information has been gathered or, in someembodiments, provide the detected reception information sequentially tothe container node controller as each subset of antenna elements hasbeen selected and the reception information for the currently selectedsubset of antenna elements has been detected.

The system's container node controller, armed with the collectedreception information for each of the selected subsets of antennaelements, then determines a location of the package ID node relative tothe system's logistics container based upon the detected receptioninformation and causes the first radio transceiver to transmit alocation message reflecting the determined location of the package IDnode relative to a storage area within the system's logistics containerto the master node. In more detail, the system's container nodecontroller may determine the relative location of the package ID nodewithin the storage area of the logistics container by comparing theobserved signal strength for each of the different selected subsets ofthe antenna elements; (b) identify one of the antenna subsets as havinga maximum observed signal strength, and (c) determine the relativelocation of the package ID node as being related to a focal area withinthe storage area for the identified antenna subset. For example,referring back to the system 6600 shown in FIG. 66, the controllermodule 66005 of exemplary container node 66000 may compare the signalstrength measured and observed by RTx unit 66480 when individually andseparately using each of antenna elements 66505 a-66505 d to identifyantenna element 66505 a as having a relative maximum of the observedsignal strengths for the broadcast signal from ID node A 66120 a. Thus,controller module 66005 may determine the relative location of thepackage ID node A 66120 a as the focal area for antenna element 66505a—i.e., the left side of container 66100A as shown in FIG. 66.

As explained above, the antenna elements used with the system's secondradio transceiver are in a dispersed configuration relative to parts ofthe system's logistics container. For example, the antenna elements maybe located in a spatially disperse configuration along an axis of thelogistics container, on different surfaces within the container (e.g.,the ceiling, door, side walls, floor), or at various locations relativeto the interior of the logistics container in a configuration thatfocuses each antenna elements' respective antenna pattern on a differentpart of the container's storage area.

Like that discussed above relative to an apparatus embodiment, thecontainer node controller in a system embodiment may generate placementfeedback information about the package ID node based upon the determinedlocation of the package ID node relative to the logistics container. Insuch a case, the system's container node controller may also cause thefirst radio transceiver to broadcast a placement feedback message to themaster node based upon the generated placement feedback information. Thesystem's container node controller may generate such placement feedbackinformation as including a loading status parameter, a current weightparameter, and/or a current balance parameter. The loading statusparameter may indicate whether the package ID node is located within thelogistics container in accordance with a loading plan for that logisticscontainer compared to the determined location of the package ID noderelative to the logistics container. The current weight parameter forthe logistics container may be based at least upon a weight of a packageassociated with the package ID node. And the current balance parameterfor the logistics container may be based at least upon the determinedlocation of the package ID node relative to the logistics container andthe weight of the package associated with the package ID node. Thus, thesystem's container node controller may be implemented with functionalitythat further enhances monitored loading/shipment/unloading operationswith such automatic and proactive messaging about placement feedback intime to avoid placement, weight, and balance related issues with the IDnode's package as it sits within the system's logistics container.

Similar to that described above on how an apparatus embodiment of theenhanced container node may be used with different types of logisticscontainers, the system embodiment's logistics container element may beimplemented in a variety of ways. For example, the logistics containermay be implemented as a unit load device (ULD) container capable ofbeing transported within an airplane; a trailer capable of being movedby a vehicle (such as a cargo trailer pulled by a truck); a train carcapable of being moved on a railway system; an intermodal shippingcontainer capable of being moved on at least two different types oftransportation modalities; a logistics storage platform, such as apalletized base platform, that supports items (e.g., ID node enabledpackages) that are being moved or transported (similar to that describedrelative to FIGS. 44-53 showing a base platform and a flexible coverthat is removably attachable to the base platform in order to secure thepackage ID node relative to the base platform); or one or more shelvescapable of supporting items (e.g., ID node enabled packages). Each ofsuch shelves may be used in a system embodiment with the containernode's multiple antenna elements to communicate with the package IDnodes supported on the shelf in a more localized manner as describedabove.

As described above, the exemplary system embodiment leverages usingmultiple antenna elements of an enhanced container node to helpdetermine a location of a package ID node relative to the containernode's logistics container. However, a further system embodiment mayalso include the master node (e.g., facility master node 66110 a asshown and explained with reference to the system 6600 shown in FIG. 66)and how it may interact with the other system elements, such asgenerating a location request relative to the package ID node andsending that location request to the container node's controller (andwhich then causes the container node controller to generate the locationcontrol message sent to the container node's second radio transceiver).Such a master node element in this system embodiment may also receivethe location determination message from the container node controllerand, in some cases, pass along such information to a server (e.g.,server 100) that reflects the determined location of the package ID noderelative to the logistics container. This master node element may alsoreceive the placement feedback message from the container nodecontroller and, in some cases, send information about the package IDnode's placement within the logistics container to the server. Such aserver may also be an additional element of an even larger systemembodiment, such as system 6600 as shown in FIG. 66.

In light of the above described different apparatus embodiments of anenhanced container node and systems embodiments that leverage use of anenhanced container node (or components of such a node), a furtherembodiment may be presented in the form of a system-level method thatfocuses on how different nodes and node elements unconventionally andadvantageously interact to help located a package ID node within alogistics container. FIGS. 69A and 69B are, collectively, a flow diagramillustrating an exemplary method implemented by a multi-antennacontainer node for locating a package ID node within a storage area ofthe logistics container in accordance with an embodiment of theinvention. Referring now to FIG. 69A, exemplary method 6900 is amulti-antenna container node implemented method of locating a package IDnode within a storage area of a logistics container, where the containernode is disposed on the logistics container and has at least a containernode controller, a first radio transceiver, and a second radiotransceiver. As noted above in more detail relative to both theapparatus and systems embodiments, an exemplary logistics containerdeployed relative to this method may come in a variety of forms (e.g., aULD, trailer, train car, intermodal shipping container, a pallet-typelogistics storage platform (that may include a cargo net to secure andcontain packages to the platform), and one or more shelf structures).Exemplary method 6900 begins at step 6905 with the container nodecontroller generating a location control message related to a package IDnode. Such a location control message may be generated in response to aninquiry message received by the container node controller from a masternode external to the logistics container (e.g., a message received bycontainer node controller module 66005 through a first radio transceiver66485 and its antenna 66500 from facility master node 110 a, which isexternal to exemplary logistics container 66100A).

At step 6910, method 6900 proceeds with the container node controller(e.g., the controller module 66005 within exemplary container node66000) sending the location control message to a second radiotransceiver of the multi-antenna container node (e.g., RTx unit 66480)having multiple antenna elements disposed in a spatially disperseconfiguration relative to the logistics container. These antennaelements provide the second radio transceiver with multi-antennawireless communication access to the package ID node disposed within thestorage area of the logistics container.

At step 6915, method 6900 proceeds with the second radio transceiveractivating or otherwise selecting a first subset of the antenna elementson the front end of the transceiver so that the second radio transceiverreceives an inbound wireless signal from the package ID node in responseto the location control message. The first subset is selected as method6900 cycles through each of the different subsets via steps 6920-6935 asdiscussed below, before step 6930 has method 6900 proceeding to step6940.

Those skilled in the art will appreciate that the subsets may includeone antenna element as a subset or may include multiple antenna elementsas a subset. For example, the second radio transceiver may simply cyclethrough each different antenna element as a subset so that thetransceiver receives signal information as each of the different antennaelements is selected and used as the antenna front end for the secondradio transceiver. However, in other embodiments, the second radiotransceiver may select different groups of the antenna elements as thedifferent subsets where the groups of antenna elements correspond to aproximity to a part of the logistics container. Thus, an example mayhave the second radio transceiver selecting two different subsets of theantenna elements—one subset being a group of the antenna elementsphysically located proximate one part of the logistics container, whilethe other subset is a group of the remaining antenna elements physicallylocated proximate the remaining part of the logistics container. Thoseskilled in the art will appreciate that deploying a larger number ofantenna elements and/or refining such groupings of the antenna elementsmay provide a way of refining the determined location as determined byembodiments described herein.

A more detailed embodiment of method 6900 may have the second radiotransceiver selecting the first subset in step 6915 by controlling whichof the different subsets of the antenna elements provides a wirelessreception input for the second radio transceiver. Thus, in an even moredetailed embodiment, the second radio transceiver may have a centralcommunicating interface and different dedicated wireless radio unitsrespectively paired and coupled to each of the different antennaelements. As such, the second radio transceiver may select differentsubsets of the antenna elements to receive the inbound wireless signalwhen the central communication interface of the second radio transceiverreceives the location control message and then selects which of thedifferent dedicated wireless radio units that are part of thetransceiver will provide reception information about the inboundwireless signal from the package ID node. When the second radiotransceiver is deployed with such different dedicated wireless radiounits (such as units 67005 a-67005 d shown in FIG. 67), selecting thedifferent dedicated radio units may involve incrementally activatingeach of the different dedicated radio units to incrementally monitor thedifferent portions of the storage area (i.e., so that each of theselected or activate different dedicated wireless radio units detects arelative signal strength of the inbound wireless signal as receptioninformation).

Controlling which of the different subsets of antenna elements mayprovide the wireless reception input for the second radio transceiver aspart of step 6915 (as well as step 6935) may also be accomplished byelectronically establishing a selective connection between a singlecentral radio unit within the second radio transceiver and the differentantenna units (e.g., as shown with mux 68005 and central radio unit68000 in FIG. 68).

At step 6920, method 6900 proceeds with the second radio transceiverdetecting reception information about the inbound wireless signal forthe selected subset of the antenna elements. Such reception informationmay be in the form of an observed signal strength of the inboundwireless signal as received through the selected subset of antennaelements. Once this is done, step 6920 proceeds to step 6925 where thesecond radio transceiver provides detected reception information to thecontainer node controller. At step 6930, if the currently selectedsubset of antenna elements is the last one, then method 6900 proceedsdirectly to step 6940. Otherwise, step 6930 moves to step 6935 where thenext subset of antenna elements is selected and method 6900 proceedsback to step 6920 to detect the relevant reception information for thatnext subset.

At step 6940, method 6900 has the container node controller determiningthe location of the package ID node relative to the logistics containerbased upon the detected reception information provided by the secondradio transceiver. Such a location may be determined as a relativelocation within the storage area of the logistics container based uponthe detected reception information provided by the second radiotransceiver (e.g., a location defined relative to parts of the storagearea—such as within a left side or a right side of the container). Inmore detail, a further embodiment of step 6940 may have the containernode controller comparing the detected reception information for each ofthe different selected subsets of the antenna elements in order toidentify one of the selected subsets of antenna elements having amaximum observed signal strength of the inbound wireless signal. Usingthis identified subset of antenna elements, the container nodecontroller may determine the relative location of the package ID nodewithin the storage area as being a location of a focal area within thestorage area for the identified one of the selected subsets of antennaelements. For example, if the second radio transceiver is coupled tofour different antenna elements and each of the antenna elements aredisposed along an axis of the logistics container, an antenna mappingfile may be stored within memory of the container node controller thatkeeps a list of antenna elements relative to particular areas of thelogistics container depending on how the antenna elements are mountedwithin the logistics container. The determining step 6940 may thus beaccomplished with the container node controller comparing the receptioninformation to identify which of the antenna element subgroups receiveda signal having the highest strength relative to what was received bythe other antenna element subgroups, and then mapping the identifiedantenna element subgroup to an area within the logistics container basedupon the antenna mapping file information. After step 6940, method 6900proceeds through transition point A to FIG. 69B.

Referring now to FIG. 69B, method 6900 continues through transitionpoint A to step 6945 where the container node controller generates alocation determination message to reflect the determined location of thepackage ID node relative to the logistics container so that, at step6950, the first radio transceiver of the multi-antenna container nodetransmits the location determination message to a master node disposedexternal to the logistics container.

A further embodiment of method 6900 may continue to step 6955 where thecontainer node controller may generate placement feedback informationabout the package ID node based upon the determined location of thepackage ID node relative to the logistics container. The placementfeedback information generated by the container node controller mayinclude a loading status parameter, a current weight parameter, and/or acurrent balance parameter. The loading status parameter indicateswhether the package ID node is located within the logistics container inaccordance with a loading plan for the logistics container (also storedas a file within the container node controller's memory) compared to thedetermined location of the package ID node relative to the logisticscontainer. The current weight parameter for the logistics container isbased at least upon a weight of a package associated with the package IDnode, which may be determined from the package's shipping informationstored within the container node controller's memory as received by thecontainer node controller from the master node or, in some embodiments,from the package's ID node. The current balance parameter for thelogistics container is based at least upon the determined location ofthe package ID node relative to the logistics container and the weightof the package associated with the package ID node.

For example, a particular logistics container may have packages andweights of such packages that are tracked by the container nodecontroller relative to their location as placed within the logisticscontainer. The particular logistics container, such as a ULD container,may have shipment and loading guidelines that identify how much weightthe container can hold altogether as well as an identified imbalancethreshold based on weight and location. The ULD may need to meet balancerequirements (e.g., center of gravity, etc.) in order to meet regulatoryrequirements for transport on an aircraft. If the ULD container has toomuch weight on one side, safety may be compromised when moving such aunbalanced ULD container. The ability of the container node controllerto automatically and proactively sense and notify other logisticsdevices about such an imbalance situation through the technicaldeployment of an enhanced container node apparatus or system using suchan enhanced container node is a technical solution to a technical andpotentially physically dangerous problem.

Finally, at step 6960, method 6900 proceeds with the first radiotransceiver transmitting such a placement feedback message to the masternode based upon the generated placement feedback information.

In summary, the embodiments described above relative to FIGS. 66, 67,68, 69A and 69B focus on apparatus, systems, and methods that involve anenhanced container node (or parts of such a node) having multipleantenna elements deployed to enhance how to locate a broadcastingpackage ID node stored within a logistics container.

Further embodiments described below relative to FIGS. 70-80 focus onapparatus, systems, and methods that involve another type of enhancedcontainer node (or parts of such a node) having multiple antennaelements used to help determine the location of a logistics containerhaving the enhanced container node (or parts of the node) within alarger physical storage, such as a storage facility, trailer, orairplane cargo compartment.

FIG. 70 is a diagram illustrating another embodiment of an exemplaryenhanced container node apparatus disposed as part of a wireless nodenetwork capable logistics container and having at least one improvedradio transceiver for reception of a node outside of the logisticscontainer as deployed in accordance with an embodiment of the invention.In general, the exemplary system shown in FIG. 70 includes server 100,network 105, and facility master node 110 a similar to that shown inFIG. 66. And similar to what is illustrated in FIG. 66, FIG. 70 shows anexemplary logistics container 70100A maintaining two packages 66130 a,66130 b. Package 66130 a is enabled with ID node A 66120 a. Likewise,package 66130 b is enabled with ID node B 66120 b. So while logisticscontainer 70100A maintains similar packages and their respective IDnodes, exemplary logistics container 70100A as shown in FIG. 70 deploysa different type of enhanced container node.

In more detail, exemplary enhanced container node 70000 is disposed onthe logistics container 70100A to generally monitor the interior ofcontainer 70100A as well as communicate with a facility master node 110a associated with a physical storage (such as a storage facility,trailer, or airplane cargo compartment). Facility master node 110 a maybe implemented as a type of wireless master node element that cancommunicate with one or more container nodes (such as container node70000) as well as electronically interact with server 100 (via network105).

Exemplary enhanced container node 70000 may be implemented with internalcomponents similar to exemplary container nodes 38000, 41000, 54000 a,or 66000 as described above but with differences related to howcontainer node 70000 implements its communication interfaces and therespective programming of their processing units. Notably, in contrastwith exemplary container node 66000 that deploys multiple antennaelements 66505 a-66505 d for interacting with the ID nodes within thelogistics container, exemplary enhanced container node 70000 makes useof multiple antenna elements 70500 a-70500 d for interacting with thefacility master node 110 a external to the logistics container.

In more detail, exemplary enhanced container node 70000 is shown havinga processing-based controller module 70005 that is operatively coupledto each of two different radio transceivers (RTx unit 70480 and RTx70485) for communicating with nodes within the logistics container70100A (e.g., ID node A 66120 a and/or ID node B 66120 b) and with nodesexternal to the logistics container 70100A (e.g., facility master node110 a) as explained in more detail below. In general, controller module70005 (also generally referred to as a container node controller) is aprocessor-based electronic computing circuit, such as a microcontroller,that contains a processing core, memory (volatile and non-volatilememory), and programmable input/output peripherals (e.g., UARTs, timers,counters, clocks, A/D and D/A converters, buffers, serial interfaces,parallel interfaces, sensors, and the like). Some embodiments ofcontroller module 70005 may be implemented as a single integratedcircuit (e.g., system on a chip (SOC) type devices) while otherembodiments may implement the container node's controller module 70005with a collection of separate circuit devices, such as a processingunit, memory, processing peripherals, and programmable interfaces asneeded for the intended container node implementation. Those skilled inthe art will appreciate that the memory within the controller module70005 is operative to maintain relevant operational data and programinstructions to support the operations as described in more detail belowwhen using such enhanced radio transceivers.

While the exemplary short range and medium/long range communicationinterfaces as described with respect to exemplary container nodes 38000,41000, or 54000 a allow for the use of separate communication paths whencommunicating with different nodes, the use of further enhanced radiotransceivers RTx unit 70480 and RTx 70485 allows the container node70000 to refine and improve how it can communicate with and locate othernodes. As shown in FIG. 70, RTx unit 70480 is generally a radiotransceiver operatively coupled to the container node controller 70005that includes an antenna 70505. As such, RTx unit 70480 facilitateswireless communication access through antenna 70505 to one or morepackage ID nodes (e.g., ID node A 66120 a and/or ID node B 66120 b)disposed within the logistics container 70100A. However, in theembodiment shown in FIG. 70, RTx unit 70485 is generally another radiotransceiver operatively coupled to the container node controller 70005that includes multiple antenna elements 70500 a-70500 d. Collectively,these antenna elements 70500 a-70500 d are disposed in a spatiallydisperse configuration relative to the logistics container 70100A andprovide RTx unit 70485 with multi-antenna wireless communication accessto facility master node 110 a, which may be fixed relative to areference position within a physical storage.

FIGS. 71 and 72 provide further details with respect to how exemplaryRTX unit 70485 may be implemented in different embodiments. Inparticular, FIG. 71 is a diagram of further internal details ofexemplary enhanced container node having a radio transceiver implementedwith multiple dedicated radio units and corresponding antenna elementsthat receive signals from outside of a logistics container in accordancewith an embodiment of the invention. Referring now to FIG. 71, exemplaryradio transceiver unit RTx 70485 is coupled to container node controllermodule 70005 and includes a central interface 71000, multiple dedicatedradio units 71005 a-71005 d, and multiple antenna elements 70500 a-70500d that each correspond to one of the dedicated radio units 71005 a-71005d. Central interface 71000 may be implemented (similar to interface67000) with switching circuitry that can provide signals and commandsfrom controller module 70005 to selective ones of the dedicated radiounits 71005 a-71005 d. Each of the dedicated radio units 71005 a-71005 dgenerally has its own radio transceiver for independent reception andtransmission of wireless signals through a corresponding one of theantenna elements 70500 a-70500 d. Those skilled in the art willappreciate that in this manner, each of the dedicated radio units 71005a-71005 d may be individually selected (e.g., via commands fromcontroller module 70005 and the switching circuitry of central interface71000) to receive or transmit information but with this architecture canalso do so simultaneously while others of dedicated radio units 71005a-71005 d receive or transmit wireless signals (or at least haveoverlapping signals being received or transmitted to other nodes).

FIG. 72 is a diagram of further internal details of an exemplaryenhanced container node having an alternative type of radio transceiverunit capable of working with multiple antenna elements. Referring now toFIG. 72, exemplary container node 70000 is shown with RTx unit 70485operatively coupled to the container node's controller module 70005 andincludes a single central radio unit 72000 that is coupled to themultiple antenna elements 70500 a-70500 d via switching circuitry 72005(generally labeled “mux” corresponding to a type of multiplexer or RFswitch). Mux 72005 may be implemented with switching circuitry that canprovide a selective communication path from an RF input/output ofcentral radio unit 72000 to and from antenna elements 70500 a-70500 d.As such, those skilled in the art will appreciate that each of theantenna elements 70500 a-70500 d may be individually selected orselected in subgroups (e.g., via commands from controller module 70005that have central radio unit 72000 controlling the switching circuitryof mux 72005) so that the central radio unit 72000 can receive ortransmit information via the selected element or subgroup of antennaelements, but does so with a single radio unit (rather than multipleradio units as shown in FIG. 71).

FIGS. 74-77 illustrate further details of various examples of logisticscontainer that may be enabled with such an enhanced container node70000. In more detail, FIGS. 74 and 75 illustrate exemplary spatiallydiverse antenna element configurations relative to a logistics containerenabled by enhanced container node 70000. Referring now to FIG. 74, anexemplary logistics container 74100A is shown having antenna elements74500 a-74500 d disposed in an exemplary configuration that is spatiallydisperse along an axis 74000 of the logistics container 74100A inaccordance with an embodiment of the invention. In this way, the antennaelements 74500 a-74500 d (similar to antenna elements 70500 a-70500 d asshown and explained relative to FIG. 70 when connected to RTx units70485, 71485, or 72485) are positioned on different points of thelogistics container 74100A. In similar fashion, FIG. 75 illustratesanother exemplary logistics container 75100A having antenna elements75500 a-75500 d disposed in an exemplary configuration spaced atdifferent corners of the logistics container 75100A in accordance withan embodiment of the invention. Still other embodiments may deployantenna elements for communication with a master node external to thelogistics container in different arrangements that separate each of theantenna elements or, alternatively, separates different groups of theantenna elements into subsets located apart from each other to leveragethat separation to help determine a refined relative position and/orangular orientation of the logistics container relative to the physicalstorage.

This aspect of physically separated and spatially diverse configurationsof the antenna elements that communicate with the master node may beshown in more detail in FIGS. 76 and 77. FIG. 76 is a diagramillustrating an exemplary embodiment of multiple wireless node networkcapable logistics containers 76100A, 76100B having axis-located antennaelements (similar to that shown in FIG. 74) and positioned within aphysical storage 76000 that is associated with a facility master node76110 a in accordance with an embodiment of the invention. As shown inFIG. 76 and explained in more detail below, an observed signal strengthof what is broadcast from facility master node 76110 a may be detectedat each of antenna elements 76500-76500 d on container 76100A (or bydifferent subgroups of such antenna elements). As described in moredetail below, the observed signal strength at each antenna element (orin some cases, an average observed signal strength for the subgroup ofantenna elements) may be compared to the broadcasted power level as sentby the facility master node 76110 a as part of determining a distance tothe master node from each antenna element or subgroup of antennaelements. With such information, an estimated relative location (such asin the form of an estimated placement region within the physicalstorage) and angular orientation may be determined by the container nodecontroller within the logistics container.

In similar fashion, FIG. 77 shows another exemplary embodiment ofmultiple wireless node network capable logistics containers 77100A,77100B having different corner-located antenna elements (similar to thatshown in FIG. 75) and positioned within physical storage 76000 that isassociated with facility master node 76110 a in accordance with anembodiment of the invention. As shown in FIG. 77, the antenna elements77500 a-77500 d on container 77100A and antenna elements 77500 e-77500 hon container 77100B are more widely dispersed on the respectivecontainers, which provides greater diversity in the determined distancesfrom the master node to each antenna element (via the observed signalstrength at each antenna element positioned in their respective pointson or as part of the logistics container). Thus, like that describedrelative to antenna elements 76500-76500 d on container 76100A, theantenna elements 77500 a-77500 d on container 77100A may be used by thecontainer node controller within the container 77100A to determine anestimated relative location (e.g., an estimated placement region withinthe physical storage 7600) and an angular orientation for container77100A.

For example, with a known location of the facility master node 76110 arelative to the physical storage 7600, the different distances from eachantenna element to the common facility master node 76110 a allows for arelative determination of location for the logistics container havingthe antenna elements (even if not with absolute coordinates). Such arelative location may be in the form of a relative distance from thefixed location of the facility master node 76110 a in the physicalstorage 76000 based upon averages of the distances from each antennaelement on the logistics container to the facility master node. Thedifferences of such antenna element to master node distances and theknown respective positions of the antenna elements as disposed on thelogistics container then allows the container node within the logisticscontainer to identify an angular orientation of the container. Suchrelative locations and angular orientations may, in some embodiments, bedetermined by the container node controller within the relevantlogistics container using reverse trilateration with the knownpositional information and relative distance information from therelevant detected reception information.

Various embodiments that use enhanced container nodes (e.g., exemplaryenhanced container node 70000) having multiple antenna elements tocommunicate with a master node may deploy and use different types oflogistics containers. For example, such a logistics container mayinclude a unit load device (ULD) container capable of being transportedwithin an airplane; a trailer capable of being moved by a vehicle; atrain car capable of being moved on a railway system; an intermodalshipping container capable of being moved on at least two differenttypes of transportation modalities; or a type of logistics storageplatform (such as a base platform and a flexible cover that is removablyattachable to the base platform in order to secure the package ID noderelative to the base platform as the logistics container or anode-enabled shelf (similar to the base platform) capable of supportingthe package ID node and a package associated with the package ID node.

Various exemplary embodiments may also deploy and use different types ofphysical storages within with to maintain such containers. For example,such a physical storage may be implemented with a unit load device (ULD)container capable of being transported within an airplane and capable ofmaintaining other types of containers; a cargo area of an airplanecapable of maintaining various ULD containers; a trailer capable ofbeing moved by a vehicle and maintaining other types of containerswithin the trailer; a train car capable of being moved on a railwaysystem and maintaining various containers within the train car's storagearea; an intermodal shipping container capable of being moved on atleast two different types of transportation modalities and within whichvarious containers may be held and maintained; as well as a physicalbuilding (such as a fixed storage facility, a designated portion of abuilding, or a designated storage area in or proximate to a building).

In light of the above discussion, an apparatus embodiment may useelements of such an enhanced container node 70000 as part of a wirelessnode network capable logistics container. In more detail, such anapparatus embodiment would include at least a container node controllerand two different radio transceivers. The container node controller,such as controller module 70005 as shown in FIGS. 70-72, is an elementof the container node 70000 that is disposed on the logistics container70100A. Being disposed on the logistics container may include beingintegrated as part of the container or as being simply attached to thecontainer in a permanent or removable manner. A first of the radiotransceivers (e.g., RTx unit 70485) is operatively coupled to thecontainer node controller and includes multiple antenna elements (e.g.,antenna elements 70500 a-70500 d) disposed in a spatially disperseconfiguration relative to the logistics container (e.g., disposed alongan axis of the logistics container (similar to that shown in FIG. 74),integrated within different parts of the logistics container, ondifferent external surfaces of the logistics container, on differentinternal surfaces of the logistics container when the material of thelogistics container allows each antenna element to receive a wirelesssignal broadcast from outside the logistics container, or near differentcorners of the logistics container (similar to that shown in FIG. 75)).In some embodiments, the spatially dispersed configuration of theantenna elements may have a first portion of the antenna elements as oneor more integrated parts of the logistics container while also having asecond portion of the antenna elements as one or more attachable antennacomponents mounted to the logistics container. These multiple antennaelements advantageously provide the first radio transceiver withmulti-antenna wireless communication access to a master node, which isassociated with the physical storage (e.g., facility master node 110 a)and disposed at a fixed position relative to the physical storage andexternal to the logistics container.

The second of the radio transceivers in this apparatus embodiment (e.g.,RTx unit 70480) is also operatively coupled to the container nodecontroller and has an antenna (e.g., antenna element 70505) providingthis radio transceiver with wireless communication access to a packageID node (e.g., ID node A 66120 a), which is disposed within thelogistics container and associated with a package (e.g., package 66130a) maintained within the logistics container.

An embodiment of the first radio transceiver may be implemented with asingle central radio unit (such as that shown in FIG. 72) that iscoupled to each of the antenna elements. However, another embodiment ofthe first radio transceiver may be implemented with multiple radio unitswhere each are respectively coupled with different antenna elements(such as that shown in FIG. 71). In more detail, the first radiotransceiver may be implemented to have a central communication interfaceoperatively coupled to the container node controller, and with each ofthe multiple dedicated radio units coupled to the central communicationinterface and one of the antenna elements. In this way, the particularantenna element coupled to each of the dedicated radio units in thefirst radio transceiver may monitor for signals emanating from themaster node.

In operation, the first radio transceiver with its multiple antennaelements and the container node controller interact in a specific,focused, unconventional and advantageous way involving furtherinteractions with the master node in order to determine a location ofthe logistics container associated with the enhanced controller nodeapparatus. In particular, the container node controller may send alocation control message to the first radio transceiver in response to alocation request message received from the master node over the firstradio transceiver. The first radio transceiver responds to the locationcontrol message by selecting different subsets of the antenna elementsto receive an inbound wireless signal from the master node. As eachsubset of antenna elements are selected (even if each subset is a singleantenna element), the first radio transceiver detects receptioninformation about the inbound wireless signal using the selected subsetof antenna elements as an active wireless reception input for the RFfront end of the transceiver. Such detected reception information maytake the form of measured or observed signal strengths of the masternode's inbound wireless signal as detected with the selected subset ofantenna elements. The first radio transceiver then provides the detectedreception information to the container node controller.

With the detected reception information from the first radio transceiver(that is in communication with the master node), the container nodecontroller determines a location of the logistics container relative tothe physical storage based upon the detected reception information fromthe first radio transceiver and then causes the first radio transceiverto transmit a location determination message to the master node. Such alocation determination message reflects the determined location of thelogistics container relative to the physical storage associated with themaster node.

In more detailed embodiments, the container node controller may use thedetected reception information relative to the different selectedsubsets of antennas in a particular manner in order to determine therelative location of the logistics container within the physicalstorage. For example, in one further apparatus embodiment, the containernode controller may determine the location of the logistics containerrelative to the physical storage based upon an average of the detectedreception information from each of the different selected subsets of theantenna elements. With spatially separated antenna elements, such anaverage may generally provide a relative location in terms of how faraway the logistics container is from the master node within the physicalstorage (e.g., within a specific range distance from the master node,and the like). This may be relevant in a general example where thephysical storage is a long trailer and a master node fixed at the frontclosed end of the trailer is in communication with the enhancedcontainer node apparatus deployed within a logistics container in thetrailer. In this example, the ability of the enhanced container nodeapparatus to determine a relative location of its associated logisticscontainer to be a certain distance from the fixed master node yields atechnical solution that aids logistics monitoring and handling of thelogistics container itself

In a further detailed embodiment, the container node controller maydetermine the location of the logistics container relative to thephysical storage by using the detected reception information to identifyan observed signal strength relative to a broadcast signal strength forthe master node's inbound wireless signal for each of the differentselected subsets of the antenna elements. Once this relative differencein observed to broadcasted signal strength information is identified foreach of the antenna element subsets, the container node controller maydetermine an estimated placement region within the physical storage forthe logistics container as the determined location of the logisticscontainer relative to the physical storage. Such an estimated placementregion is based upon the identified relative observed signal strengthsof the inbound wireless signal as associated with the respectivepositions for each of the different selected subsets of the antennaelements. For example, the container node controller may determine thebroadcast signal strength of the master node's inbound wireless signalfrom information in the signal's package header. With the differentobserved signal strengths detected at the positions known for each ofthe subsets of antenna elements relative to the logistics container, thecontainer node controller is able to use reverse trilateration todetermine the estimated placement region within the physical storage. Inother words, the container node controller may identify the observedsignal strength relative to the broadcast signal strength for the masternode's inbound wireless signal as indicated by a broadcast power settingparameter in a header of the inbound wireless signal, and then determinethe estimated placement region using reverse trilateration based uponthe fixed position of the master node relative to the physical storage.

In even more detail, an embodiment may have the apparatus' containernode controller able to determine the location of the logisticscontainer relative to the physical storage by first identifying anangular orientation of the logistics container relative to the masternode based upon the identified relative observed signal strength of theinbound wireless signal as associated with a respective position foreach of the different selected subsets of the antenna elements. Basedupon (1) the identified relative observed signal strength of the inboundwireless signal as associated with a respective position for each of thedifferent selected subsets of the antenna elements and (2) theidentified angular orientation of the logistics container relative tothe master node, the container node controller may then identify arefined relative position of the logistics container within the physicalstorage for the logistics container as the determined location of thelogistics container relative to the physical storage. Thus, the knownspatial disposition of the different antenna elements may be used andleveraged by the apparatus' container node controller and the multipleantenna element based first radio transceiver to help determine arelative position of the logistics container within a physical storageassociated with the master node through such interactions between thesespecific nodes and node elements.

In a further extension of the above detailed embodiment, the locationdetermination message generated by the container node controller mayinclude further information other than just the location of thelogistics container relative to the physical storage. For example, sucha location determination message may also reflect the identified angularorientation of the logistics container relative to the physical storageassociated with the master node.

In another example, the container node controller may maintain loadingplan information for the physical space within its memory storage. Suchloading plan information may be preloaded into the container nodecontroller or sent to the container node controller via the master nodeto identify different containers and their intended locations within thephysical space. In such an embodiment, the location determinationmessage may also include a loading status parameter proactivelyinforming the master node whether the logistics container is locatedwithin the physical storage in accordance with the loading plan for thephysical storage compared to the determined location of the logisticscontainer relative to the physical storage. This may advantageously helpoffload some of the physical space monitoring tasks normally performedby the master node associated with the physical space.

Thus, exemplary embodiments of an enhanced container node apparatus(e.g., such as that shown in FIG. 70) may be deployed to use multipleantenna elements in communication with a master node to determine alocation of the logistics container associated with the enhancedcontainer node apparatus.

While the above description relates to an exemplary enhanced containernode apparatus that communicates with a master node via multiple antennaelements, such an apparatus may be deployed as part of a larger systemembodiment that includes the logistics container as a component. In someexamples of such a system embodiment, some or all of the elements makingup such an enhanced container node may be built into and be anintegrated part of the logistics container. However, in other examples,the container node with its multiple antenna elements may be disposed onthe logistics container when operating as the system but in aconfiguration that has the container node being removable andreplaceable and/or with antenna elements that may be removably placed atdifferent locations on logistics container.

In more detail, an exemplary embodiment of an enhanced wireless nodenetwork capable container system, such as that shown in FIG. 70,generally includes a logistics container, a container node controller,and two different radio transceivers—one of which having multipleantenna elements. The system's container node controller (such ascontroller module 70005) is disposed on the logistics container—e.g., inan attached or integrated manner relative to an accessible storage areawithin the logistics container 70100A or in a removable manner using anattachable housing for the container node 70000 within which thecontainer node controller 70005 is disposed.

The system's first radio transceiver (e.g., RTx unit 70485) isoperatively coupled to the container node controller and has multipleantenna elements (e.g., antenna elements 70500 a-70500 d) placed in adispersed configuration relative to the logistics container so as toprovide reception/transmission coverage that is spread out on differentparts of the logistics container (e.g., similar to that shown in FIGS.74 and 75). As such, the antenna elements provide the first radiotransceiver with multi-antenna wireless communication access to a masternode (e.g., facility master node 110 a) disposed external to thelogistics container. For example, as shown in FIG. 70, antenna elements70500 a-70500 d are disposed in different parts of logistics container70100A to provide RTx unit 70485 of container node 70000 withmulti-antenna wireless access to facility master node 110 a (i.e.,multiple reception locations with which to receive a signal beingbroadcast from master node 110 a). While the system's second radiotransceiver (e.g., RTx unit 70480) is also operatively coupled to thecontainer node controller, this second transceiver and has an antenna(e.g., antenna element 70505, which may be implemented as anomni-directional antenna) providing wireless communication access to apackage ID node disposed with a package maintained within the logisticscontainer.

In operation, those skilled in the art will appreciate that this systemembodiment's container node controller and the different radiotransceivers interoperate as discussed above relative to the apparatusembodiment of an enhanced container node apparatus embodiment thatdeploys multiple antenna elements to communicate with a master node aspart of determining a location of the logistics container. Additionally,a system embodiment may also include the logistics container in additionto the controller node controller and the two enhanced radiotransceivers.

A further embodiment of such a system embodiment may also include themaster node that is disposed external to the system's logisticscontainer at the fixed position relative to the physical storage. Forexample, such a further system embodiment may generally compriselogistics container 70100A, container node controller 70005 (as disposedwithin container node 70000 that is on the container 70100A), a firstradio transceiver implemented with RTx unit 70485 and antenna elements70500 a-70500 d, a second radio transceiver implemented as RTx unit70480 with antenna 70505, and facility master node 110 a that is locatedat a fixed position relative to a physical storage and that broadcasts asignal for reception by actively selected subsets of antenna elements70500 a-70500 d in order to determine the relative location and/orangular orientation of container 70100A related to the physical storage.The master node in this system embodiment may be operative to generate alocation request relative to the logistics container and transmit thatlocation request to the container node's controller via the first radiotransceiver (which then causes the container node controller to generatethe location control message sent to the container node's first radiotransceiver). Such a master node element in this system embodiment mayalso receive the location determination message from the container nodecontroller and, in some cases, pass along information to a server (e.g.,server 100) that reflects the determined location of the package ID noderelative to the logistics container. Such a server may also be anexplicit element of a larger system embodiment, such as system 7000 asshown in FIG. 70.

In light of the above described different apparatus and systemsembodiments leveraging use of an enhanced container node (or componentsof such a node) that deploy multiple antenna elements when communicatingwith a master node external to the container node's logistics container,a further embodiment may be presented in the form of a system-levelmethod that focuses on how different nodes and node elementscollectively and advantageously interact in an unconventional manner tohelp determine a relative location of the logistics container withrespect to the physical storage associated with the master node. FIG. 78is a flow diagram illustrating an exemplary method implemented by amulti-antenna container node for locating the logistics containerrelative to a physical storage associated with a master node inaccordance with an embodiment of the invention. Exemplary method 7800,as shown and explained relative to FIG. 78, is directed to amulti-antenna container node implemented method of locating a package IDnode within a storage area of a logistics container, where the containernode is disposed on the logistics container and has at least a containernode controller, a first radio transceiver, and a second radiotransceiver. An exemplary logistics container deployed relative to animplementation of method 7800 may come in a variety of forms (e.g., aULD, trailer, train car, intermodal shipping container, a pallet-typelogistics storage platform (that may include a cargo net to secure andcontain packages to the platform), and one or more shelf structures). Anexemplary physical storage associated with the master node deployedrelative to an implementation of method 7800 may also come in a varietyof forms (e.g., a unit load device (ULD) container capable of beingtransported within an airplane and capable of maintaining other types ofcontainers; a cargo area of an airplane capable of maintaining variousULD containers; a trailer capable of being moved by a vehicle andmaintaining other types of containers within the trailer; a train carcapable of being moved on a railway system and maintaining variouscontainers within the train car's storage area; an intermodal shippingcontainer capable of being moved on at least two different types oftransportation modalities and within which various containers may beheld and maintained; as well as a physical building (such as a fixedstorage facility, a designated portion of a building, or a designatedstorage area in or proximate to a building)).

Exemplary method 7800 begins at step 6905 where the container nodecontroller generates a location control message related to a position ofthe controller node's logistics container. This step may, for example,be performed by the container node controller after having received alocation request message from the master node associated with thephysical storage. In a particular example, server 100 may receive arequest to determine a location of a particular logistics container77100A (as shown in FIG. 77) and, as a result, sends the facility masternode 76110 a associated with physical storage 7600 an inquiry aboutlogistics container 77100A. Facility master node 76110 a may service theserver's inquiry by sending the location request message to thecontainer node controller within logistics container 77100A. Based uponsuch a received location request message, the container node controller(such as controller module 70005) generates the relevant locationcontrol message.

At step 7810, method 7800 has the container node controller of themulti-antenna container node (e.g., container node 70000) sending thelocation control message to the first radio transceiver of themulti-antenna container node (e.g., RTx unit 70485). The first radiotransceiver used in method 7800 has antenna elements disposed in aspatially disperse configuration relative to the logistics container. Inthis manner, the multiple antenna elements (e.g., antenna elements70500A-70500 d) as disposed relative to different parts of the logisticscontainer provide the first radio transceiver with multi-antennawireless communication access to the master node disposed external tothe logistics container. For example, the spatially disperseconfiguration of the antenna elements relative to the logisticscontainer may have the antenna elements disposed along an axis of thelogistics container (similar to that shown in FIG. 74); integratedwithin different parts of the logistics container (such as a top orcorners of the logistics container); disposed on or attached todifferent external surfaces of the logistics container; disposed on orattached to different internal surfaces of the logistics container whenthe material of the logistics container allows each antenna element toreceive a wireless signal broadcast from outside the logisticscontainer; or near different corners of the logistics container (similarto that shown in FIG. 75)). In some embodiments of method 7800, thespatially dispersed configuration of the antenna elements may have afirst portion of the antenna elements as one or more integrated parts ofthe logistics container while also having a second portion of theantenna elements as one or more attachable antenna components mounted tothe logistics container. These multiple antenna elements advantageouslyprovide the first radio transceiver with multi-antenna wirelesscommunication access to a master node, which is associated with thephysical storage (e.g., facility master node 110 a) and disposed at afixed position relative to the physical storage and external to thelogistics container.

At step 7815, method 7800 proceeds by having the first radiotransceiver, in response to the location control message from thecontainer node controller, selecting a first subset of the first radiotransceiver's antenna elements. This may be a single antenna elementlocated at a particular position on the logistics container, or in otherexamples, may be several of the antenna elements grouped as the firstsubset near the particular position on the logistics container. Theselected first subset of antenna elements may then be coupled orconnected to an RF front end of the first radio transceiver so as toallow for a purposefully selective reception of an inbound wirelesssignal broadcast from the master node via just the selected subset ofantenna elements (as explained in more detail relative to step 7820). Inother words, the first radio transceiver may control which of thedifferent subsets of its antenna elements to selectively activate inorder to provide an active wireless reception input for the first radiotransceiver through the selected subset of antenna elements.

At step 7820, method 7800 continues with the first radio transceiverdetecting reception information about the inbound wireless signal fromthe master node using the selected subset of the antenna elements. Inparticular, the detected reception information may be in the form of anobserved signal strength of the inbound wireless signal from the masternode for the selected subset of the antenna elements. Method 7800 waitsin step 7820 until the reception information using the selected subsetof antenna elements has been captured or detected before method 7800moves to step 7825 where the first radio transceiver provides thedetected reception information to the container node controller.

At step 7830, method 7800 proceeds to step 7840 if the current subset ofantenna elements is the last of the subsets, but otherwise proceeds tostep 7835 to have the first radio transceiver select the next subset ofantenna elements and continue back to step 7820.

At step 7840, method 7800 has the container node controller determine alocation of the logistics container relative to the physical storagebased upon the detected reception information from the first radiotransceiver. In some instances, the location of the logistics containerrelative to the physical storage may be determined based upon an averageof the detected reception information from each of the differentselected subsets of the antenna elements. For example, as shown in FIG.77, the detected reception information from each of the corner antennaelements 77500 a-77500 d positioned at corner locations of logisticscontainer 77100A may allow the container node controller withinlogistics container 77100A to determine the location of container 77100Abased upon an average of the observed signal strengths at each of thecorner antenna elements 77500 a-77500 d.

In a more detailed embodiment of method 7800, step 7840 may be performedby the container node by identifying observed signal strengths and usingknown positional information for the antenna element subsets as part ofdetermining an estimated placement region within the physical storage tobe where the logistics container is located. Specifically, in such adetailed embodiment, the container node controller may first use thedetected reception information to identify an observed signal strengthrelative to a broadcast signal strength for the master node'sbroadcasted signal (e.g., as indicated by a broadcast power settingparameters in the header of the master node's broadcasted signal) foreach of the different selected subsets of the antenna elements. Thecontainer node controller then may record an association in its memoryof each of identified relative observed signal strengths of the masternode's wireless signal with a respective position for each of thedifferent selected subsets of the antenna elements. Thus, with thepositional information within the controller's memory on where thedifferent subsets of antenna elements lie with respect to the logisticscontainer and with the identified observed signal strengths asassociated with the positional information, the container nodecontroller may then determine an estimated placement region within thephysical storage for the logistics container as the determined locationof the logistics container relative to the physical storage. Such adetermination may use, for example, reverse trilateration based upon thefixed position of the master node relative to the physical storage, therelative signal strength information and the positional information onthe different antenna element subsets.

In still a further embodiment, the container node controller maydetermine the location of the logistics container relative to thephysical storage as a refined position based upon an identified angularorientation of the logistics container. In particular, the containernode may first identify an angular orientation of the logisticscontainer relative to the master node based upon the identified relativeobserved signal strength of the inbound wireless signal as associatedwith a respective position for each of the different selected subsets ofthe antenna elements. Based upon the identified relative observed signalstrength of the inbound wireless signal as associated with a respectiveposition for each of the different selected subsets of the antennaelements and the identified angular orientation of the logisticscontainer relative to the master node, the container node controller maythen identify a refined relative position of the logistics containerwithin the physical storage for the logistics container as thedetermined location of the logistics container relative to the physicalstorage. Such a refined relative position may include a distancecomponent indicating generally how far the logistics container islocated relative to the fixed location of the master node within thephysical space and an angular orientation component indicating generallyhow the logistics container is oriented (e.g., with a certain side ofthe logistics container being closest to the master node's locationbased on the differences in observed signal strengths at differentantenna element subsets).

At step 7845, method 7800 concludes with the first radio transceiver ofthe multi-antenna container node transmitting a location determinationmessage (as generated by the container node controller) to the masternode where the location determination message reflects the determinedlocation of the logistics container relative to the physical storageassociated with the master node. In a further embodiment, such alocation determination message may reflect an identified angularorientation of the logistics container relative to the physical storageassociated with the master node. And in still another embodiment, such alocation determination message may include a loading status parameterinforming the master node whether the logistics container is locatedwithin the physical storage in accordance with a loading plan for thephysical storage when compared to the determined location of thelogistics container relative to the physical storage. Such a loadingplan may be stored within a memory on the multi-antenna container nodeand accessible by the container node controller. For example, a frontpart of the physical storage near a doorway may be designed for items orpackages that are supposed to be unloaded first but loaded in last givenproximity to the doorway of the storage. Accordingly, an exemplaryloading plan file stored within the container node controller (e.g.,preloaded or provided on request by a master node, such as the masternode associated with the storage) may indicate that the logisticscontainer is supposed to be placed in the front part of the physicalstorage. However, if the container node controller communicates in amanner as described above with the master node and used its multipleantennas to determine the location of its logistics container is, infact, in a rear part of the physical storage, the container nodecontroller may set the loading status parameter part of the locationdetermination message sent to the master node to include a misloadcondition particular to that logistics container as positioned withinthe physical storage so that the master node, or a server incommunication with the master node, may further automatically andproactive notify logistics personnel related to the physical storage(e.g., via messaging to a user access device, such as a smartphone ortablet based device operating as a type of ID node).

Those skilled in the art will appreciate that a further combination typeof embodiment of an enhanced container node apparatus may determine therelative location of the package ID node within the container with afirst group of multiple antenna elements (similar to that shown in FIG.66) and also may also determine a relative location of the logisticscontainer within a physical storage using a second group of multipleantenna elements (similar to that shown in FIG. 70). This generallycombines the related multi-antenna components (e.g., antenna elementsand their associated enhanced radio transceivers) to provide thefunctionality of a container node disposed on a logistics container thatoperates as described above relative to both exemplary enhancedcontainer node 66000 and exemplary enhanced container node 70000. Such afurther combination apparatus embodiment is depicted in more detail inFIG. 73, which illustrates such an exemplary combination enhancedcontainer node apparatus 73000 disposed as part of a wireless nodenetwork capable logistics container 73100A and having one improved radiotransceiver 70485 for reception of signals from master node 110 aoutside of the logistics container 73100A and a second improved radiotransceiver 66480 for reception of signals from a package ID node 66120a inside of the logistics container 73100A. As shown in FIG. 73, thoseskilled in the art will appreciate that container node controller 73005within container node 73000 is operative to interact with RTx unit 66480and its multiple antenna elements 66505 a-66505 d for communicating withand locating an ID node within the logistics container 73100A in amanner as described above relative to FIGS. 66, 67, 68, 69A, and 69B.Likewise, container controller node 73005 is also operative in thisembodiment to interact with RTx unit 70485 and its multiple antennaelements 70500 a-70500 d for communicating with facility master node 110a and locating container 73100A within a physical storage associatedwith the facility master node as described above relative to FIGS. 70-73and 74-78. Thus, FIG. 73 presents a combination type of embodiment thatdeploys a different multi-antenna, multi-radio transceivers as part ofanother type of enhanced container node in an apparatus embodiment; asystem embodiment that uses such an apparatus and may also include thelogistics container, facility master node, and server as these elementsare deployed relative to each and interact as described above; and amethod embodiment that combines the operations as presented in thecombined flow diagrams of FIGS. 69A, 69B, and 78 as described above.

As described above relative to FIGS. 44-53, an exemplary platform-basedlogistics container may be associated with a type of container node. Ageneral embodiment of this type of platform-based logistics containermay be implemented as a logistics storage platform having a mechanicalbase that essentially supports items (e.g., ID node enabled packages)that are being stored, moved or transported on a central support surfaceof the base. This type of exemplary logistics container may also includea flexible cover (such as cargo netting) that is removable and attachesto the base platform in order to secure one or more node enabledpackages relative to the base platform as previously described above.

Another example of such a platform-based logistics container is when thebase platform is implemented as a shelf type of platform (such asshelving disposed in a building, in a delivery vehicle, or mountedwithin a larger logistics container). Such a shelf may be implemented assupport surface base and, in some embodiments, may include multipleshelves and may include walls to further provide container support toany items maintained on the shelf. And, like the other logisticscontainers described above, such a shelf or platform-based logisticscontainer may be enabled with an enhanced container node having multipleantenna elements. FIGS. 79-82 provide further details of differentembodiments of exemplary logistics containers that may be coupled to andused with an enhanced container node (e.g., enhanced container nodes66000 or 73000) having multiple antenna elements for determining alocation of a package ID node.

In more detail, FIG. 79 is a diagram illustrating an alternativeembodiment of a logistics container implemented as an exemplarylogistics storage platform for securing, storing, transporting ID nodeenabled packages in accordance with an embodiment of the invention.Referring now to FIG. 79, enhanced container node enabled logisticsstorage platform 79100A is shown as being similar to exemplary baseplatform 4400 of FIG. 44 in that it includes a central support surface4405 surrounded by rail type of edge structure 4410 on the periphery ofthe base platform 4400. Similar to base platform 4400 shown in FIG. 53,platform 79100A may use the same type of exemplary cover 5300 (e.g.,cargo netting) having multiple cover attachment points that can betemporarily secured to different base attachment points disposed alongthe edges of the base of platform 79100A (e.g., base attachment pointsillustrated in FIGS. 48-49 that attach within channels disposed withinthe rail edge structure of similar base platform 4400). And similar tobase platform 4400 of FIG. 44, platform 79100A as shown in FIG. 79 hasan enhanced type of container node secured within a channel 4415 a alongthe periphery of the base of platform 79100A (shown in more detail inFIG. 80). Additionally, the container node deployed with platform 79100Ais an exemplary enhanced container node having multiple antenna elementsfor communicating with package ID nodes being supported on the platform79100A.

FIG. 80 is a more detail diagram illustrating an exemplary system 8000that has a server 100, a facility master node 110 a in communicationwith the server 100, and an exemplary enhanced container node 80000 thatcommunicates with the facility master node 110 a through antenna 80500.Exemplary enhanced container node 80000 is further shown as beingattached to platform 79100A, but those skilled in the art willappreciate that node 80000 may be attached, secured, or integrated intoto other parts of platform 79100A. Exemplary enhanced container node80000 is shown having multiple antenna elements 80505 a-80505 d disposednear the corners of platform 79100A. In this manner, each of antennaelements 80505 a-80505 d may have a characteristic antenna pattern forreception and transmission that is focused on different parts of thesupport surface of platform 79100A. While shown being disposed near orat the corners of platform 79100A, those skilled in the art willappreciate that other embodiments may have the antenna elements 80505a-80505 c spatially disposed on or within platform 79100A along an axisof the logistics storage platform,

Those skilled in the art will appreciate that enhanced container node80000, similar to enhanced container node 66000, includes a controllermodule and two radio transceiver units similar to container nodecontroller module 66005 and RTx units 66485, 66480. As such, each of theantenna elements 80505 a-80505 d are coupled to RF input/outputs of oneof the radio transceiver units within container node 80000 so thatselective ones of the antenna elements 80505 a-80505 d may communicatewith an ID nodes associated with a package supported on platform 79100,such as ID node 80120 a within package 5200 a as shown in FIG. 80.

In operation and as shown in FIG. 80, the antenna elements 80505 a-80505d are deployed and used with platform-based enhanced container node80000 for localized tracking and locating of particular ID nodes inpackages that are supported on platform 79100A. More particularly, theradio transceiver within node 80000 connected to antenna elements 80505a-80505 c may receive a location control message from the container nodecontroller within node 80000. In response, the radio transceiver selectsdifferent subsets of the antenna elements 80505 a-80505 d to receive aninbound wireless signal from package ID node 80120 a. For example, theradio transceiver in node 80000 may selectively use each corner locatedindividual antenna element as a subset. In this manner, the radiotransceiver may cycle through each antenna element to selectively detectreception information about the inbound wireless signal from package IDnode 80120 a. The radio transceiver then provides the detected receptioninformation to the container node controller within enhanced containernode 80000—e.g., as the reception information is incrementally capturedfor each of the subsets or in a collective burst with receptioninformation provided for all of the subsets.

With this reception information (e.g., observed signal strengthmeasurements for the detected inbound wireless signal from package IDnode 80120 a), the container node controller determines a location ofthe package ID node 80120 a relative to the logistics storage platform79100A based upon the detected reception information, and then causesthe other radio transceiver to transmit a location message to the masternode reflecting the determined location of the package ID node 80120 arelative to the logistics storage platform 79100A. For example, thecontainer node controller within platform-based enhanced container node80000 may compare each of the observed signal strength measurements madewhen selectively connecting one of the radio transceivers within node80000 to individual ones of antenna elements 80505 a-80505 d. As shownin FIG. 80, an observed signal strength of the signal broadcast from IDnode 80120 a would be the greatest when received through antenna element80505 c. As a result, the container node controller within node 80000may determine the location of package ID node 80120 a as a relativelocation (e.g., in a quadrant of platform 79100A closest to the focalarea of antenna element 80505 c) and then have a location message sentto master node 110 a reflecting that localized measurement-basedlocation determination.

Similar to other enhanced container node embodiments described above,the container node controller within enhanced container node 80000 maygenerate placement feedback information about package ID node 80120 abased upon the determined location of the package ID node 80120 arelative to logistics storage platform 79100A, and cause one of theradio transceivers in node 80000 to broadcast a placement feedbackmessage to the facility master node 110 a over antenna 80500 based uponthe generated placement feedback information. Such placement feedbackinformation may include a loading status parameter, a current weightparameter, and a current balance parameter similar to that previouslydescribed. For example, the loading status parameter may indicatewhether the package ID node is located on the logistics storage platform79100A in accordance with a loading plan for that logistics storageplatform 79100A compared to the determined location of the package IDnode 80120 a relative to the logistics storage platform 79100A. Anexemplary current weight parameter for the logistics storage platform79100A may be based at least upon a weight of package 5200 a associatedwith the package ID node 80120 a. And an exemplary current balanceparameter for the logistics storage platform 79100A may be based atleast upon the determined location of the package ID node 80120 a on thelogistics storage platform 79100A and the weight of the package 5200 aassociated with the package ID node 80120 a.

Similar principles may be applied to a system that deploys multipleplatform-based logistics container using one or more shelves capable ofsupporting items (e.g., ID node enabled packages). Each of such shelvesmay be associated with an enhanced container node (similar to node80000) deployed with multiple antenna elements to communicate with thepackage ID nodes supported on that shelf in a localized manner allowingfor container node measurement-based location determinations. FIG. 81 isa diagram illustrating such an alternative embodiment of a logisticscontainer that uses shelving platforms for securing, storing, andtransporting ID node enabled packages in accordance with an embodimentof the invention. Referring now to FIG. 81, shelf 81100A is shownsimilar to platform 79100A in that shelf 81100A is another example of aplatform-based logistics container enhanced with container node 80000and its multiple antenna elements 80505 a-80505 d. Exemplary shelf81000A, along with shelves 81100B and 81100C, may be attached to acommon backside wall 81105 to form an enhanced container node enabledshelving system 8105. This exemplary shelving system 8105 may beimplemented as standalone shelving or built-in shelving relative to astorage area, building, mobile conveyance, or the like where each shelfin such a system may be container node enabled so that each node-enabledshelf may actively use its multiple antenna elements disposed relativeto its shelf structure to determine the location of a particular ID noderelative to the shelf.

Such a shelving system 8105 may further operate as part of a largersystem 8100 via communication with a facility master node 110 a, whichis in further communication with server 100. As such, system 8100 may beimplemented to track and management movement of packages, such aspackage 5200 a shown supported on shelf 81100A. The enhanced containernode 80000 may operate as described above to determine the location ofpackage ID node 80120 a relative to shelf 81100A and notify master node110 a regarding the determined location. Facility master node 110 a mayfurther update server with information on the determined location of thepackage ID node 80120 a (and its package 5200 a).

Such a node-enabled shelving system may also be implemented, as shown inFIG. 82, with various side walls relative to one or more of the shelvesso that the antenna elements may be mounted on or within the baseplatform of the shelf as well as one or more of the side walls. Forexample, as shown in FIG. 82, another embodiment of an enhanced nodeenabled shelving system 8205 has multiple shelves 81100A-81100C, acommon backside wall 81105, and side walls 82000 a-82000 d. In thismanner, antenna elements, such as elements 80505 a-80505 d, may bedisposed relative to node-enabled shelf 81100A on the shelf itself, onside wall 82000 a, side wall 82000 b, and backside wall 81105 in aspatially diverse configuration so that the different antenna patternsfocus on not only different two-dimensional locations relative to theshelf 81100A but may also provide reception granularity in a thirddimension (i.e., height above the shelf) via selective subsets ofantenna elements disposed at different heights above the shelf 81100A.Thus, the multiple antenna elements used to help locate a package IDnode supported on shelf 81100A may be disposed on or built into a topsurface of the shelf's base platform, a bottom surface of the shelf'sbase platform, a side wall surface relative to the shelf, and aninterior part of the shelf.

Use of Dedicated Listening Receivers and Command Radios in WirelessNodes

As described above, different embodiments of a wireless node networkused in logistics and shipping operations may use multiple radioelements to enhance certain monitoring operations related tonode-enabled packages being shipped, such as determining the location ofthe node-enabled packages and the location of a container relative to amaster node enabled physical storage space. Still further embodimentsmay have an improved type of wireless monitoring node within such awireless node network where the node uses special dedicated radiotransceivers to help enhance and improve monitoring of low-level IDnodes. In particular, this type of monitoring node may have one or morededicated listener radio receivers that can scan/listen for broadcastsignals from low-level package associated ID nodes on particularchannels (e.g., a particular frequency) at the same time, while alsohaving one or more separately dedicated command radio transceivers tocommunicate instructions (e.g., association instructions, power changinginstructions, etc.) to such low-level ID nodes. The low-level ID nodesmay be programmed by this type of monitoring node via such instructionsto advertise or broadcast in a desired way. For example, the ID nodesmay be instructed to change how the ID node broadcasts using aparticular broadcast profile or specific parameters within a broadcastprofile (e.g., instructions that change how a low-level ID nodebroadcasts at a particular signal power level, broadcasts on aparticular signal frequency, and/or broadcasts according to timingparameters that set how often the particular ID node transmits (or howlong to wait before transmitting a next signal). With the low-level IDnodes broadcasting as instructed, the monitoring node may assign thedifferent dedicated listener or node monitoring radio receivers tolisten to a particular channel (e.g., frequency) such that the receiversare assigned to different channels so as not miss overlapping orsimultaneous broadcasts from the different low-level ID nodes.

Deploying such separate dedicated command transmitters and dedicatednode monitoring receivers enhances this type of monitoring node'sability to handle dense node environments where the monitoring node mayinteract with a relatively large number of low-level ID nodes. In someembodiments, programming or providing instructions to differentlow-level ID nodes may be much more time consuming than just listeningfor relevant signals. Thus, using exemplary embodiments of this type ofmonitoring node helps the node avoid spending too much time in aprogramming mode sending instructions to low-level ID nodes and, as aresult, be a more effective listener to handle and monitor morecongested logistics environments, such as large storage facilities,aircraft cargo storage compartments, and other large conveyances thatmay temporarily store and transport ID node enabled items being shipped.FIGS. 83-86 provide further details of various exemplary apparatus,system, and method embodiments related to this type of monitoring nodeand how it may be leveraged in wireless node logistics monitoringsolutions that yield enhanced and improved monitoring results in anunconventional and advantageous manner.

FIG. 83 is a diagram illustrating an embodiment of an exemplarydedicated multi-radio system and apparatus for logistics node monitoringdisposed in a wireless node network having a plurality of low-level IDnodes and a high-level managing node, wherein each of the low-level IDnodes is associated with one of a plurality of items being shipped inaccordance with an embodiment of the invention. Referring now to FIG.83, an exemplary system 8300 is shown having a high-level managing node83100, a mid-level monitoring node 83000, and multiple packages 83130a-83130 c (each having a respective ID node 83120 a-83120 c). Ingeneral, exemplary mid-level monitoring node 83000 may be implementedwith processing, memory, and general peripheral circuitry as describedrelative to an exemplary master node 110 a or an exemplary containernode described above but with specialized short range communicationinterfaces implemented with separate dedicated command radio anddedicated monitoring receivers that can handle overlapping programmingevents and overlapping ID node signal broadcasts. In more detail,exemplary mid-level monitoring node 83000 is shown in FIG. 83 as havinga central node control processor 83200 (similar to the processingelements described relative to an exemplary master node or containernode) that is operatively coupled to a remote management communicationinterface 83485 (which is connected to antenna 83500). As such, theremote management communication interface 83485 (and antenna 83500)provides the central node control processor 83200 with communicationaccess to the high-level managing node 83100 (e.g., a server or a masternode that interacts with mid-level monitoring node 83000).

While central node control processor 83200 uses remote managementcommunication interface 83485 to communicate with elements higher withinthe network, such as high-level managing node 83100, processor 83200 isalso operatively coupled to two different types of dedicated radioelements that interact with low-level ID nodes—namely, a dedicatedcommand radio transceiver and a separate dedicated node monitoring radioreceiver. A general embodiment of mid-level monitoring node 83200 mayinclude one or more of each. In more detail and as shown in FIG. 83,central node control processor 83200 of exemplary mid-level monitoringnode 83000 is coupled to a first and second command radio transceiver(i.e., command RTx units 83400 a, 83400 b). The first command radiotransceiver 83400 a is dedicated to providing the central node controlprocessor 83200 with a first command interface to multiple low-level IDnodes, such as ID node A 83120 a, ID node B 83120 b, and ID node C 83120c. As such and using this dedicated type of first command interface, thefirst command radio transceiver 83400 a, in response to a nodeinstruction command received by the central node control processor 83200from the high-level managing node 83100, may be controlled to transmitan ID node instruction from the central node control processor 83200 toat least one of the low-level ID nodes, such as ID node A 83120 a. SuchID node instructions are commands intended to be processed by thereceiving ID node to change its operation. For example, such an ID nodeinstruction may include a node association operation instruction causingthe receiving low-level ID node to responsively establish a permittednode relationship with another node element in the wireless nodenetwork; a node broadcast operation instruction causing the receivinglow-level ID node to responsively alter a broadcasting status; aninstruction causing the receiving low-level ID node to responsivelyalter a broadcasting power level; an instruction causing the at leastone of the receiving low-level ID node to responsively alter abroadcasting timing parameter; and a node data transmission operationinstruction causing the receiving low-level ID node to responsivelybroadcast data gathered by that ID node (e.g., sensor data related to apackage associated with the ID node or sensor data received by that IDnode from another ID node that has shared the sensor data).

The second command radio transceiver 83400 b similarly provides thecentral node control processor 83200 with a parallel command interfaceto the low-level ID nodes (e.g., ID node A 83120 a, ID node B 83120 b,and ID node C 83120 c). This parallel command interface allows thesecond command radio transceiver 83400 b, in response to another nodeinstruction command received by the central node control processor 83200from the high-level managing node 83100, may be controlled to transmitanother ID node instruction from the central node control processor83200 to another of the low-level ID nodes while the first command radiotransceiver 83400 a transmits the ID node instruction to one of thelow-level ID nodes. In this manner, the first command interface providedby the first command radio transceiver 83400 a and the parallel commandinterface provided by the second command radio transceiver 83400 b maybe established and used as part of an embodiment of mid-level monitoringnode 83000 to permit at least overlapping communication of differentcommand instructions to different ones of the low-level ID nodes.

In addition to the dedicated command radio transceivers 83400 a-83400 b,the central node control processor 83200 in exemplary mid-levelmonitoring node 83000 is coupled to multiple node monitoring radioreceivers—e.g., node monitoring radio Rx units 83405 a-83405 c. Thefirst node monitoring radio receiver 83405 a is operatively coupled tothe central node control processor 83200 and assigned by the centralnode control processor 83200 to listen for one or more signals from atleast one of the low-level ID nodes 83120 a-83120 c over a first channel(e.g. a first range of frequencies). The second node monitoring radioreceiver 83405 b is also operatively coupled to the central node controlprocessor 83200 and may be assigned by the central node controlprocessor 83200 to listen for signals broadcast by the low-level IDnodes 83120 a-83120 c over a second channel (e.g. a second range offrequencies) simultaneously as the first node monitoring radio receiver83405 a listens for signals from these low-level ID nodes over the firstchannel such that the first channel does not overlap with the secondchannel. Similarly, the third node monitoring radio receiver 83405 c isalso operatively coupled to the central node control processor 83200 andmay be assigned by the central node control processor 83200 to listenfor signals from at least one of the low-level ID nodes 83120 a-83120 cover a third channel (e.g. a first range of frequencies) simultaneouslyas each of the first node monitoring radio receiver 83405 a and thesecond node monitoring radio receiver 83405 b listens for signals fromat least one of the low-level ID nodes such that the third channel isdistinct from the first channel and the second channel.

In more detail, exemplary central node control processor 83200 isprogrammed to responsively assign these radio receiver units 83405a-83405 c based upon monitoring commands received from the high-levelmanaging node. For example, central node control processor 83200 assignsthe first node monitoring radio receiver 83405 a to listen for one ormore signals from the low-level ID nodes 83120 a-83120 c over the firstchannel in response to a first monitoring command received over theremote management communication interface 83485 from the high-levelmanaging node 83100. Similarly, the central node control processor 83200may assign the second node monitoring radio receiver 83405 b to listenfor the one or more signals from the low-level ID nodes 83120 a-83120 cover the second channel in response to a second monitoring commandreceived over the remote management communication interface 83485 fromthe high-level managing node 83100. Likewise, the central node controlprocessor 83200 may assign the third node monitoring radio receiver83405 c to listen for one or more signals from the low-level ID nodes83120 a-83120 c over the third channel in response to a third monitoringcommand received over the remote management communication interface83485 from the high-level managing node 83100.

Thus, a dedicated multi-radio apparatus for logistics node monitoringdisposed in a wireless node network may be deployed to improve how tocontrol and monitor low-level ID nodes associated with packages beingshipped. Such an exemplary multi-radio apparatus deployed as mid-levelmonitoring node may be used in a system that includes at least themid-level monitoring node (e.g., mid-level monitoring node 83000) andthe high-level monitoring node (e.g., high-level monitoring node 83100implemented as a server or a master node type of network element).

A further more detailed system embodiment may be deployed having such ahigh-level managing node, the mid-level monitoring node, and at least afirst low-level ID node disposed relative to a first package beingshipped and a second low-level ID node disposed relative to a secondpackage being shipped. For example, as shown in FIG. 83, such anexemplary system 8300 may include high-level managing node 83100, themid-level monitoring node 83000 as described above, a first low-level IDnode 83120 a disposed relative to package 83130 a being shipped and asecond low-level ID node 83120 b disposed relative to package 83130 bbeing shipped. The high-level managing node 83100 is disposed in thewireless node network and at least maintains association informationrelating the first low-level ID node 83120 a and package 83130 a andmaintains association information relating the second low-level ID node83120 b and the second package 83130 b. The mid-level monitoring node83000, also disposed in the wireless node network, communicated with thehigh-level managing node 83100 as noted above, and is operative tomonitor for one or more signals from at least one of the first low-levelID node and the second low-level ID node in response to a control inputmessage received from the high-level managing node 83100 using thecomponents of exemplary mid-level monitoring node 83000 described above.

Specifically, the system's mid-level monitoring node comprises at leasta central node control processor, one or more command radiotransceivers, and one or more node monitoring radio receivers. In thisexemplary system embodiment, the central node control processor isprogrammed to operate as described above relative to processor 83200 tobe responsible for coordinating the monitoring for the one or moresignals from the first low-level ID node 83120 a and the secondlow-level ID node 83120 b. The remote management communication interface(e.g., interface 83485) is operatively coupled to the central nodecontrol processor 83200 and provides the central node control processorwith access to the high-level managing node and the control inputmessage from the high-level managing node. Each of the command radiotransceivers are operatively coupled to the central node controlprocessor and respectively dedicated to providing the central nodecontrol processor with different command interfaces to each of the firstlow-level ID node and the second low-level ID node. Such a commandinterface allows the respective command radio transceiver to an ID nodeinstruction from the central node control processor to one of the firstlow-level ID node and the second low-level ID node based upon thecontrol input message. And similar to that described above regardingexemplary mid-level monitoring node 83000, each of the node monitoringradio receivers in the system's mid-level monitoring node is operativelycoupled to the central node control processor and assigned by thecentral node control processor to listen for the one or more signalsfrom at least one of the first low-level ID node and the secondlow-level ID node over a first channel.

In operation, the mid-level monitoring node and its components interactin an unconventional manner when conducting logistics monitoring as partof such a system. In more detail, FIG. 84 is a flow diagram illustratingan exemplary method for logistics node monitoring in a wireless nodenetwork using a dedicated multi-radio mid-level monitoring nodeapparatus with a high-level managing node and multiple low-level IDnodes associated with different items being shipped in accordance withan embodiment of the invention. Referring now to FIG. 84, method 8400begins at step 8405 where the high-level managing node generates acontrol input message and transmits the control input message to themid-level monitoring node. The high-level managing node may beimplemented as a server or a master node that communicates with themid-level monitoring node through its remote management communicationinterface. Such a high-level managing node may generate and transmit thecontrol input message as a command formatted for the mid-levelmonitoring node that alters how components of the mid-level monitoringnode are configured for multi-radio element monitoring and controllingof low-level ID nodes.

At step 8410, method 8400 has the remote management communicationinterface on the mid-level monitoring node receiving the control inputmessage from the high-level managing node. For example, remotemanagement communication interface 83485 of exemplary mid-levelmonitoring node 83000 may receive information representing the controlinput message from the high-level managing node 83100 through antenna83500 and pass the received control input message information to thecentral node control processor 83200 so that the central node controlprocessor 83200 may implement changes in response to the control inputmessage.

At step 8415, method 8400 continues with the central node controlprocessor generating an ID node instruction in response to the controlinput message. As noted before, examples of different ID nodeinstructions may include, but are not limited to, a node associationoperation instruction that causes an ID node to responsively establish apermitted node relationship with another node element in the wirelessnode network; a node broadcast operation instruction that causes an IDnode to responsively alter a broadcasting status (e.g., an instructioncausing the ID node to responsively alter a broadcasting power level oralter a broadcasting timing parameter); and a node data transmissionoperation instruction causing an ID node to responsively broadcast datagathered by that ID node (such as sensor data related to a packageassociated with that ID node).

At step 8420, method 8400 proceeds with the first command radiotransceiver on the mid-level monitoring node transmitting the generatedID node instruction to at least one of the low-level ID nodes. As adedicated command radio transceiver, the first command radio transceiverprovides the mid-level monitoring node with a first dedicated commandinterface to the low-level ID nodes. In some embodiments of method 8400,additional ID node instructions may be generated and transmitted toother ID nodes through steps similar to step 8415 and 8420 using asecond command radio transceiver on the mid-level monitoring node. Assuch, the second command radio transceiver in this extension of method8400 provides the central node control processor with a parallel commandinterface to the low-level ID nodes. Stated another way, the firstcommand interface provided by the first command radio transceiver andthe parallel command interface provided by the second command radiotransceiver permits at least overlapping communication of differentcommand instructions to different ones of the low-level ID nodes. Thoseskilled in the art will appreciate that method 8400 may be extendedfurther with additional versions of steps 8415 and 8420 for stillfurther ID node instructions that are transmitted to other ID nodes viaa third or more command radio transceiver.

In this way, step 8420 may be performed in response to a first nodeinstruction command received over the remote management communicationinterface from the high-level managing node. Likewise, those skilled inthe art will appreciate that when a second command radio transceiver isinvolved, the step of transmitting the additional ID node instructionvia this second command radio transceiver may be performed in responseto a second node instruction command received over the remote managementcommunication interface from the high-level managing node.

At steps 8425 and 8430, method 8400 turns to configuring the mid-levelmonitoring node's dedicated monitoring radio receiver(s). Thus, at step8425, method 8400 proceeds with the central node control processorgenerating a first assignment instruction for a first node monitoringradio receiver on the mid-level monitoring node. In more detail, thisfirst assignment instruction is a command generated by the central nodecontrol processor that assigns the first node monitoring radio receiverto listen for one or more signals from the low-level ID nodes over thefirst channel (e.g., a particular frequency or frequency range) inresponse to a first monitoring command received by the processor overthe remote management communication interface from the high-levelmanaging node. In a further embodiment, method 8400 may also have thecentral node control processor generating a second assignmentinstruction as part of step 8425 that assigns a second node monitoringradio receiver to listen for one or more signals from the low-level IDnodes over a second channel in response to a second monitoring commandreceived over the remote management communication interface from thehigh-level managing node. In similar fashion, still another embodimentof method 8400 may have the central node control processor generating athird assignment instruction as part of step 8425 that assigns the thirdnode monitoring radio receiver to listen for one or more signals fromthe low-level ID nodes over a third channel in response to a thirdmonitoring command received over the remote management communicationinterface from the high-level managing node.

At step 8430, method 8400 proceeds with the central node controlprocessor in the mid-level monitoring node sending the generated firstassignment instruction to the first node monitoring radio receiver tocause the first node monitoring radio receiver to listen for one or moresignals from at least one of the low-level ID nodes over the firstchannel (e.g., a first frequency, first set of frequencies, or a firstsubset of ID nodes deemed to belong to a first channel). A similar stepis performed in the further embodiments described above for generatedsecond and third assignment instructions relative to respective secondand third node monitoring radio receivers disposed as part of themid-level monitoring node. In this way, the second assignmentinstruction to the second node monitoring radio receiver causes thesecond node monitoring radio receiver to listen for one or more signalsfrom at least one of the low-level ID nodes over the second channelsimultaneously as the first node monitoring radio receiver listens forthe one or more signals from at least one of the low-level ID nodes overthe first channel, where the first channel does not overlap with thesecond channel. Likewise, the third assignment instruction to the thirdnode monitoring radio receiver causes the third node monitoring radioreceiver to listen for one or more signals from at least one of thelow-level ID nodes over a third channel simultaneously as each of thefirst node monitoring radio receiver and the second node monitoringradio receiver listens for the signals from at least one of thelow-level ID nodes, where the third channel is distinct from the firstchannel and the second channel.

Upon completion of method 8400, the specialized and dedicated radioelements of the mid-level monitoring node have been programmaticallyconfigured so that the mid-level monitoring node enters an enhancedmonitoring state of operation to better handle congested nodeenvironments with, for example, a large number of package ID nodesdeployed as low-level ID nodes in the network.

As shown in FIG. 83, an embodiment of exemplary mid-level monitoringnode 83000 may include the radio receivers and transceivers asincorporated or integrated parts of the mid-level monitoring node.However, alternative embodiments of an exemplary mid-level monitoringnode may deploy some of the radio elements as separate devices externalto mid-level monitoring node. For example, FIG. 85 is a diagramillustrating such an alternative embodiment of an exemplary dedicatedmulti-radio system and apparatus for logistics node monitoring disposedin a wireless node network in accordance with an embodiment of theinvention. Referring now to FIG. 85, exemplary system 8500 is shown withan exemplary mid-level monitoring node 85000 in communication withhigh-level managing node 83100 (as described above) as well as incommunication with ID node A 83120 a, ID node B 83120 b, and ID node C83120 c (each of which being related to respective different packages83130 a-83130 c being shipped and monitored). In general, exemplarymid-level monitoring node 85000 shown in FIG. 85 is similar to exemplarymid-level monitoring node 83000 shown in FIG. 83. Both have componentsthat are dedicated command radio units and dedicated node monitoringradio units. However, as shown in FIG. 85, some of the dedicated radiocomponents may be implemented as integrated parts of the mid-levelmonitoring node 85000 while others of the dedicated radio components maybe implemented as physically separate devices from node 85000. Relativeto such physically separate dedicated radio units, the mid-levelmonitoring node 85000 may operate as a remote manager for the separatededicated radio units.

In more detail, the embodiment of a dedicated multi-radio system 8500for logistics node monitoring is disposed in a wireless node networkhaving a plurality of low-level ID nodes 83120 a-83120 c and high-levelmanaging node 83100 (such as a server or master node). In oneembodiment, the system may include the mid-level monitoring node 85000and one or more node monitoring radio receiver units 85405 a-85405 c incommunication with the mid-level monitoring node 85000 as separatedevices. In general, the mid-level monitoring node 85000 coordinatesmonitoring for one or more signals from at least one of the low-level IDnodes 83120 a-83120 c in response to a control input (e.g., a messagewith control information or other commands for node 85000) from thehigh-level managing node 83100.

Similar to node 83000, the exemplary mid-level monitoring node 85000 insystem 8500 further comprises a central node control processor 85200, aremote management communication interface 85485, one or more commandradio transceivers 85400 a-85400 c, and a monitoring radio communicationinterface 85600. In this embodiment, the central node control processor85200 is configured and programmed so that it operates to coordinatemonitoring for one or more signals from at least one of the low-level IDnodes 83120 a-83120 c. The remote management communication interface85485 (similar to interface 83485) is operatively coupled to the centralnode control processor 85200 and provides the central node controlprocessor 85200 with communication access via its antenna 85500 to thehigh-level managing node 83100. As such, the remote managementcommunication interface 85485 receives the control input from thehigh-level managing node 83100 through its antenna 85500 and passes thatcontrol input to the central node control processor 85200.

All of the command radio transceivers 85400 a-85400 c are operativelycoupled to the central node control processor 85200. As such, each ofthe command radio transceivers is dedicated to providing the centralnode control processor 85200 with a different command interface to thelow-level ID nodes 83120 a-83120 c. For example, a first command radiotransceivers 85400 a provides a first command interface for the centralnode control processor 85200, which allows for transmission of a firstID node instruction from the central node control processor 85200 of themid-level monitoring node 85000 to at least one of the low-level IDnodes 83120 a-83120 c. Thus, the different command interfaces providedby each of the command radio transceivers 85400 a-85400 c may operate inparallel. As such, these different command interfaces using thedifferent command radio transceivers 85400 a-85400 c of node 85000permit at least overlapping communication of different commandinstructions (e.g., one or more of the different types of ID nodeinstructions as explained above) to different ones of the low-level IDnodes 83120 a-83120 c.

The monitoring radio communication interface 85600 of mid-levelmonitoring node 85000 is also operatively coupled to the central nodecontrol processor 85200. In one embodiment, in response to feedbackreceived by the monitoring radio communication interface 85600 from thecentral node control processor 85200 related to the control inputreceived from high-level managing node 83100, the monitoring radiocommunication interface 85600 may generate and send different assignmentinstructions to different ones of the separate dedicated node monitoringradio receivers 85405 a-85405 c. However, in other embodiments, themonitoring radio communication interface 85600 may operate more as aswitching interface to pass along relevant assignment instructionsgenerated by the central node control processor 85200 to specific onesof the separate dedicated node monitoring radio receivers 85405 a-85405c.

As mentioned above, each of the dedicated node monitoring radioreceivers 85405 a-85405 c is separately disposed relative to mid-levelmonitoring node 85000 and is in communication with the mid-levelmonitoring node 85000 through the monitoring radio communicationinterface 85600. Each of these distinct and separate dedicated nodemonitoring radio receivers 85405 a-85405 c may be responsive toassignment instructions received from the mid-level monitoring node85000 to listen for one or more signals from at least one of thelow-level ID nodes 83120 a-83120 c over a first channel. In someembodiments, there may be a single dedicated node monitoring radioreceiver deployed separate from mid-level monitoring node 85000 (such asreceiver 85405 a), but in other embodiments multiple separate receiversmay be deployed. For example, mid-level monitoring node 85000 is shownin FIG. 85 in communication with a second separate dedicated nodemonitoring radio receiver 85405 b, which is responsive to a secondassignment instruction to listen for one or more signals from at leastone the low-level ID nodes 83120 a-83120 c over a second channelsimultaneously as the first node monitoring radio receiver unit 85405 alistens for one or more signals from at least one of the low-level IDnodes 83120 a-83120 c over the first channel, where the first channeldoes not overlap with the second channel. Mid-level monitoring node85000 is also shown in FIG. 85 in communication with a third separatededicated node monitoring radio receiver 85405 c, which is responsive toa third assignment instruction to listen for one or more signals from atleast one the low-level ID nodes 83120 a-83120 c over a third channelsimultaneously as each of the first node monitoring radio receiver unit85405 a and the second node monitoring radio receiver unit 85405 blistens for signals from the low-level ID nodes 83120 a-83120 c wherethe third channel is distinct from the first channel and the secondchannel. As noted above, such channels may be considered particularsignal frequencies or frequency ranges that different from one another.

Thus, the different node monitoring radio receiver units may detectdifferent signals in their respective channels at the same time andprovide different detection notifications back to the mid-levelmonitoring node 85000. For example, one node monitoring radio receiverunit 85405 a may transmit a first detection notification to themonitoring radio interface 85600 of the mid-level monitoring node 85000.Such a first detection notification reflects the detection of anysignals from at least one of the low-level ID nodes 83120 a-83120 c overthe first channel. At the same time, a second node monitoring radioreceiver unit 85405 b may transmit a second detection notification tothe monitoring radio interface 85600 of the mid-level monitoring node85000. Such a second detection notification reflects detection of anysignals from at least one of the low-level ID nodes 83120 a over thesecond channel while the first node monitoring radio receiver unit 85400a detects a signal from at least one of the low-level ID nodes 83120a-83120 c over the first channel.

Another system embodiment may focus on a dedicated multi-radio systemfor logistics node monitoring disposed in a wireless node network havingat least two low-level ID nodes (such as ID nodes 83120 a, 83120 bassociated with respective packages 83130 a, 83130 b being shipped) anda high-level managing node (such as high-level managing node 83100 thatmay be implemented as a server or master node. This system embodimentgenerally comprises a mid-level monitoring node (such as node 85000) andtwo separate node monitoring radio receiver units. The mid-levelmonitoring node has communication access to the high-level managing nodeover a first communication path (such as a longer range Wi-Fi orcellular formatted communication path) and communication access to thetwo low-level ID nodes over a second communication path (such as ashorter range BLE formatted communication path). The mid-levelmonitoring node in this embodiment is responsive to a control inputreceived from the high-level managing node over the first communicationpath to generate multiple monitoring assignment task instructionsrelated to scanning for one or more signals from the low-level ID nodes.

A first of the node monitoring radio receiver units (such as nodemonitoring radio receiver 85405 a) is responsive to a first of themonitoring assignment task instructions to scan for one or more signalsfrom the low-level ID nodes over a first channel (e.g., a specificfrequency or range of frequencies). This first monitoring assignmenttask instruction is received by the first node monitoring radio receiverover a third communication path (wired or wireless) connecting theseparate radio receiver unit and the mid-level monitoring node.

A second of the node monitoring radio receiver units (such as nodemonitoring radio receiver 85405 b) is responsive to a second of themonitoring assignment task instructions to scan for one or more signalsfrom the low-level ID nodes over a second channel (e.g., anotherfrequency or range of frequencies different from and does not overlapwith that associated with the first channel) simultaneously while thefirst node monitoring radio receiver unit scans for the one or moresignals from the low-level ID nodes over the first channel. In thisconfiguration, the second monitoring assignment task instruction isreceived by the second node monitoring radio receiver over the thirdcommunication path from the mid-level monitoring node.

The mid-level monitoring node in this alternative system embodiment mayinclude multiple command radio transceivers (such as command radiotransceivers 85400 a-85400 c) that respectively provide differentcommand interfaces to different ID nodes and permit at least overlappingcommunication of different command instructions (e.g., different ID nodeinstructions as explained above0 to different ones of the low-level IDnodes.

Still a further embodiment may deploy programmable dedicated multi-moderadio elements as part of an exemplary mid-level monitoring node basedapparatus or system. In these embodiments, the multi-mode radio elementsare generally programmable radio transceivers that may be selectivelyassigned to operate as either a dedicated command radio transceiver thatsends ID node instructions to particular ID nodes or a dedicated nodemonitoring radio receiver setup and programmatically configured tolisten for signals from an ID node at a particular frequency orfrequency range. The ability to selectively deploy multi-mode or radioelements capable of being programmed to handle different dedicatedtransmitter/receiver tasks (i.e., different command and node monitoringroles) within the exemplary mid-level monitoring node allows the samemid-level monitoring node to be used as an apparatus or an element of alarger system embodiment to handle complex and changing node landscapeswhere some of the multi-mode radio elements may be changed from adedicated command radio transceiver to a dedicated node monitoring radioreceiver unit.

FIG. 86 is a diagram providing further details of such an alternativeembodiment of an exemplary dedicated multi-mode radio based apparatusand system for logistics node monitoring disposed in a wireless nodenetwork in accordance with an embodiment of the invention. Referring nowto FIG. 86, exemplary system 8600 is shown having high-level managingnode 83100 (e.g., implemented as a server or master node) thatcommunicates with an exemplary mid-level monitoring node 86000, which isspecially composed and configured to communicate with multiple low-levelID nodes 83120 a-83120 c associated with respective packages 83130a-83130 c being shipped. Similar to nodes 83000 and 85000, exemplarymid-level monitoring node 86000 includes a central node controlprocessor 86200 that may communicate with high-level managing node 83100through remote management communication interface 86485 (similar tointerfaces 83485 and 85485) and antenna 86500.

Exemplary mid-level monitoring node 86000 further includes multiplemulti-mode radio transceiver units 86405 a-86405 d (labeled as“Multimode RTx Unit” devices on FIG. 86). Each of the multi-mode radiotransceiver units 86405 a-86405 d are operatively coupled to the centralnode control processor 86200, which controls the particular mode inwhich the respective multi-mode radio transceiver unit will operate. Ina system embodiment, the high-level managing node 83100 may providecontrol input information to the processor 86200 of mid-level monitoringnode 86000 in order to assign or program the particular mode statedesired for each of the multi-mode radio transceivers 86405 a-86405 d.In response, central node control processor 86200 may generate andtransmit appropriate mode comments to each of the multi-mode radiotransceivers 86405 a-86405 d. As such, each of the multi-mode radiotransceivers 86405 a-86405 d may be selectively configured vis suchprogrammatic commands to operate as a dedicated command radiotransceiver or a dedicated node monitoring radio receiver.

For example, as shown in FIG. 86, exemplary multi-mode radio transceiverunits 86405 c and 86405 d have received specific mode commands fromcentral node control processor 86200 to temporarily place each of theserespective units into a dedicated command mode state. As such,multi-mode radio transceiver unit 86405 c enters a mode state where itis dedicated to providing a command interface where one or more ID nodeinstructions are transmitted to ID node B 83120 b while multi-mode radiotransceiver unit 86405 d enters a mode where it is dedicated toproviding a different or parallel command interface where one or more IDnode instructions are transmitted to ID node C 83120 c while unit 86405c transmits ID node instructions to ID node B 83120 b. In this manner,two of the multi-mode radio transceiver units within exemplary mid-levelmonitoring node 86000 may be programmatically configured as needed forthe monitoring environment faced by node 86000 when deployed in ashipment application when multiple low-level ID nodes need to beconfigured in an overlapping manner (e.g., have different ID nodeinstructions transmitted as at least overlapping communications) orre-configured via node 86000.

Further, in the example shown in FIG. 86, exemplary multi-mode radiotransceiver units 86405 a and 86405 b have received specific modecommands from central node control processor 86200 to temporarily placeeach of these respective units into a dedicated node monitoring radioreceiver mode state. As such, multi-mode radio transceiver unit 86405 alistens for one or more signals from at least one of the low-level IDnodes 83120 a-83120 c over a first designated channel (e.g., a firstfrequency range) while multi-mode radio transceiver unit 86405 b listensfor one or more signals from at least one of the low-level ID nodes83120 a-83120 c over a second designated channel (e.g., a secondfrequency range). In this manner, the other two of the multi-mode radiotransceiver units within exemplary mid-level monitoring node 86000 maybe programmatically configured as needed for the monitoring environmentfaced by node 86000 when deployed in a shipment application whenmultiple low-level ID nodes need to be separately and simultaneouslymonitored via node 86000 over different frequency ranges so as not tomiss receiving ID node broadcast events.

Thus, as shown in FIG. 86, a system embodiment may generally comprisethe high-level managing node 83100 and elements of the exemplarymid-level monitoring node 86000 (such as the multi-mode radiotransceiver units) as described above as interactive components that canbe configured to provide selective dedicated command interfaces anddedicated node monitoring receivers when managing and monitoringmultiple ID node enabled packages being shipped. A further systemembodiment may focus on such a mid-level monitoring node 86000 (and itsmulti-mode radio transceiver units) and include two or more of thelow-level ID nodes 83120 a-83120 c associated with respective packages83130 a-83130 c being shipped. Still another system embodiment may focuson the larger system 8600, which may generally comprise the high-levelmanaging node 83100, elements of the exemplary mid-level monitoring node86000 (such as the multi-mode radio transceiver units) as describedabove as interactive components that can be configured to provideselective dedicated command interfaces and dedicated node monitoringreceivers, and two or more ID node enabled packages being shipped.

Improved Communications in Congested Node Landscapes

As previously described, an exemplary ID node may be considered alow-level wireless sensor-based processing node device that may beincluded, attached, paired or otherwise logically associated with anitem being shipped and as an electronic sensor-based device thatmonitors the item and its condition before, during, and/or aftershipment as well as interacting with other wireless nodes that arecollectively part of a logistics network of nodes. Also, as previouslydescribed, such ID nodes may be controlled and monitored by differentinteracting elements of the logistics network of hierarchically relateddevices, such as other ID nodes, master nodes, container nodes, andservers.

As such logistics networks of hierarchically related devices grow largerin number of nodes and denser in terms of operating nodes in a givenarea, the different devices may encounter communication problems due tonode congestion. Stated another way, when the density of activelogistics-related nodes of a logistics network in a given area becomestoo large, the electronic landscape may become so active that somedevices in the logistics network cannot properly communicate with otherdevices in the logistics network. As a result, controlling andmonitoring package-related ID nodes can become increasingly difficultbased upon the operating node density. Thus, the operating node densitycan negatively impact communication between interacting elements of thelogistics network (such as a package ID node reporting sensorinformation relevant to its associated package to a master node or whena package ID node requests association permission to become associatedwith another master node given movement and a new location of thepackage ID node).

For example, a shipping and logistics company may operate a packageshipment processing facility that temporarily stores a large number ofnode-enabled packages as part of shipping such packages. Additionally,such a facility may have different delivery vehicles unloading morenode-enabled packages for temporary storage within the facility, whileother delivery vehicles are being loaded with some of the temporarilystored node-enabled packages. Thus, the shipment processing facility mayhave an extremely high operating node density at certain times andrelative to certain locations within the facility (which can create nodecommunication problems), while the facility may have lower operatingnode densities at other times and at other locations. To address suchproblems faced when operating node density exceeds a tolerablethreshold, an embodiment of logistics-related node elements can beactively managed by a server or at least one master node in a logisticswireless node network in an advantageously unconventional manner thatsuccessfully accommodates higher operating node densities while allowingfor successful controlling and monitoring of the different node elementsat the same time.

In general, such an embodiment may deploy a managing element (e.g., aserver or master node) that may be programmed to use a type ofcommunication “pruning” technique where a neighboring node near atargeted node for communication is instructed to stop broadcasting for aspecific time interval so that the target node may communicate with lesspotential interference during that time interval. This helps to takepressure off communications with the target node during that timeinterval and, also, provides time for the node landscape surrounding thetarget node to change so that an updated operating node density mayimprove to where such communication pruning is no longer needed.

This type of pruning may take place for one or more different nodes nearthe target node (e.g., incrementally changing a broadcast profile foreach of the different nodes so that the same node is not “pruned” tostop broadcasting for too long). Such pruning may also take place withclusters of nodes that are treated the same way (e.g., changing abroadcast profile for all nodes in a particular cluster or group ofnodes or incrementally doing so for different clusters of the nodes nearthe target node). As described in more detail below relative to FIGS.87A-99, different embodiments may leverage such unconventional pruningand clustering techniques as performed by different types of managingelements disposed within a logistics node network.

In more detail, FIGS. 87A-87D are related diagrams illustrating anexemplary system of logistics node elements that include an exemplaryserver as a type of managing element that provides enhancedcommunication management for a congested node environment in accordancewith one or more embodiments of the invention. Referring now to FIG.87A, an exemplary enhanced system 8700 for communication management isshown with server 87100, master nodes 87110 a, 87110 b, and ID nodesID1-ID21. Server 87100 is shown deployed as an exemplary managingelement of the wireless node networked system 8700 and may beimplemented based on exemplary server 100 as explained in more detailabove relative to FIG. 5 with further programmatic modifications asexplained in more detail below relative to FIG. 90. As shown in FIG.87A, server 87100 communicates with master nodes 87110 a and 87110 b viaa direct communication path (e.g., Wi-Fi, cellular, or the like) whileserver 87100 may communicate indirectly with ID nodes ID1-ID21 via anindirect communication path through at least one of the master nodes87110 a, 87110 b and that further uses a short range communication path(e.g., BLE formatted communications) between that respective master nodeand one or more of the ID nodes. Thus, the indirect communication pathuses at least one of the master nodes (and may use one or more ID nodes)as an intermediary type of node between a specific ID node and server87100.

As part of exemplary communication management system 8700, the masternodes 87110 a and 87110 b and ID nodes ID1-ID21 are respectively locatedat different locations. For example, master node 87110 a is shown asbeing generally located relative to a storage location A 87205 where itmay monitor and communicate with other nodes in that vicinity(represented by the concentric circles centered upon the location ofmaster node 87110 a). Storage location A 87205 may, for instance, beimplemented as a temporary storage room within a shipment processingfacility, a storage area within a tractor trailer, or a cargo area of anaircraft used to transport shipments. In the example shown in FIG. 87A,master node 87110 b is generally located relative to a delivery vehiclestorage area 87210 of such a shipment processing facility and is mayalso monitor and communicate with other nodes in that vicinity(represented by the concentric circles centered upon the location ofmaster node 87110 b). The delivery vehicle storage area 87210 in thisexample may be configured to receive packages or items for delivery viaone or more delivery vehicles (as shown expressly in FIGS. 89A-89B).Furthermore, delivery vehicle storage area 87210 may be linked withstorage location A 87205 by an exemplary conveyor system 87200, whichessentially operates to help move the packages or items from the storagelocation A 87205 into the delivery vehicle storage area 87210. Thoseskilled in the art will appreciate that ID node enabled packages anditems may be moved manually or via other types of transport mechanismsbetween locations have different master nodes in other embodiments wherenode congestion issues may arise.

As shown in FIG. 87A, each of ID nodes ID1-ID21 are generally pairedwith one or more of such packages or items being shipped. Those skilledin the art will appreciate that while exemplary ID nodes ID1-ID21 areshown in FIG. 87A, their respective related or paired package or item isnot explicitly shown for purpose of clarity and to avoid excessivelycrowding the illustration in FIG. 87A. Thus, the symbol for each of IDnodes ID1-ID21 represents an exemplary ID node (such as ID node 120 aexplained above relative to FIG. 3) and may also represent such an IDnode along with its included, attached, paired or otherwise logicallyassociated respective package(s) or item(s) (e.g., an ID node includedin the box of a packaged item being shipped along with other relatedpackages).

In the initial configuration shown in FIG. 87A, exemplary ID nodesID1-ID16 are disposed as a group near to and within communication rangeof master node 87110 a at the storage location A 87205. For example, IDnodes ID1-ID16 may be contained within a single storage bin or containerso that the nodes are in relative close proximity to each other. IDnodes ID17 and ID18 are also within communication range of master node87110 a and at storage location A 87205, but are located apart from thegroup of ID nodes ID1-ID16. For example, ID nodes ID17 and ID may havejust arrived (with their respective items being shipped) at storagelocation A 87205 while the group of ID nodes ID1-ID16 (with theirrespective items being shipped) may be temporarily held in a particularholding area of the storage location A 87205 separate from whereincoming packages may arrive. Further, ID nodes ID19-ID21 (with theirrespective items being shipped) are shown as being moved from storagelocation A 87205 to delivery vehicle storage area 87210 (and from withinthe communication range of master node 87110 a to within thecommunication range of master node 87110 b) via conveyor system 87200.

In FIG. 87B, exemplary server 87100 begins to programmatically implementenhanced communication management techniques that would allow for morerobust communications between the nodes shown, especially in light ofthe congestion environment of ID nodes ID1-ID16. In particular,exemplary server 87100 executes communication management softwareprogram code and instructions (such as high density node communicationmanagement code 90000 shown in FIG. 90 that may be part of the server'scontrol and management code as described above) to programmaticallytransform the server's functionality with a collection of operativesteps that help improve how nodes can communicate in dense nodeenvironments. As such, server 87100 is operative to identify one of thewireless nodes (e.g., a master node or ID node) as a “target” node at aninitial location so that enhanced management steps may be further takenby server 87100 to enhance and improve the ability of that target nodeto successfully communicate in the operating node environmentsurrounding the target node.

For example, as shown in FIG. 87B, server 87100 may identify ID node ID1as the target node located within the communication range of master node87110 a and identify that ID node ID1 is surrounded by the group of IDnodes ID2-ID16 proximate to the initial location of ID node ID1. Next,server 87100 determines the operating node density of this group of IDnodes relative to ID node ID1 relative to a threshold node densityvalue. For example, server 87100 may determine that within a certaindistance range relative to ID node ID1 the operating node density iscurrently 15 operating nodes for those that fall within that range(i.e., the group of ID nodes ID2-ID16). If the operating node densitythreshold is set at 5 nodes, then server 87100 identifies that targetnode ID1 is currently in an overly congested node environment given thedetermined operating node density exceeds this threshold. As a result,the server 87100 is then operative to transmit a change in a broadcastprofile to at least one neighboring node from the group of ID nodesID2-ID16 proximate to the initial location of the target node ID1. Forexample, in the embodiment shown in FIG. 87B, exemplary server 87100 maycause ID node ID2 to change its broadcast profile so that ID node ID2temporarily ceases broadcasting during a first time interval. Here, IDnode ID2 may be selected for this type of “pruning” or temporary ceasein broadcasting because ID node ID2 may be determined by server 87100 asbeing located closest to the target ID node ID relative to a least amajority of the remaining nodes in the group of ID nodes ID2-ID16. Inanother example, server 87100 may select ID node ID2 because it has beenbroadcasting at a higher signal power level than others in the group ofID nodes ID2-ID16.

In other embodiments, more than one neighboring node may be pruned. Forexample, in the embodiment shown in FIG. 87C, exemplary server 87100 mayalternatively cause multiple nodes (such as ID nodes ID 2-ID6) from theinitial group of nodes proximate to target ID node ID (i.e., ID nodesID2-ID16) to temporarily cease broadcasting for the first time interval.Thus, each of ID nodes ID2-ID6 are shown in shaded form to representthat they have been selected for “pruning” by the server 87100 so thatall of ID nodes ID2-ID6 temporarily cease broadcasting during the firsttime interval. This subgroup of ID nodes ID2-ID6 from the initiallyidentified group of proximate nodes ID2-ID16 relative to the location oftarget ID node ID1 is an example of how the server 87100 may identify IDnodes ID2-ID6 as a subgroup cluster of nodes from the initiallyidentified group of proximate nodes ID2-ID16 that collectively representat least one neighboring node to the target node ID node ID1 in thisparticular embodiment.

In a further embodiment, exemplary server 87100 may cause one or moredifferent nodes in the subgroup ID2-ID6 to incrementally ceasebroadcasting temporarily during one or more parts of the first timeinterval rather than have all nodes in the subgroup cluster of nodestemporarily cease broadcasting during that whole time interval. Forexample, server 87100 may cause ID node ID2 to temporarily ceasebroadcasting for a first part of the first time interval, and thenswitch to causing ID node ID3 to temporarily cease broadcasting for asecond part of the first time interval. This may continue for each ofthe ID nodes ID4-6 so that different ones of ID nodes ID2-ID6 areinstructed to temporarily cease broadcasting in a sequential order(which may be selected randomly within this subgroup cluster or basedupon power levels being otherwise broadcast and/or frequencies used bythose nodes in the subgroup cluster). Alternatively, server 87100 maybreak up the different nodes in the subgroup cluster of nodes ID2-ID6into further subgroups (e.g., first causing both nodes ID2 and ID3 totemporarily cease broadcasting, then causing both ID nodes ID4 and ID 5to temporarily cease broadcasting, and the like). Still a furtherembodiment may have server 87100 causing two or more different nodes inthe subgroup ID2-ID6 to cease broadcasting temporarily in at least anoverlapping fashion during one or more parts of the first time intervalrather than have all nodes in the subgroup cluster of nodes temporarilycease broadcasting.

In the embodiment shown in FIG. 87D, server 87100 may have causedanother subgroup cluster of nodes (i.e., ID nodes ID7-ID16) from theinitial group of nodes (i.e., ID nodes ID2-ID16) proximate to target IDnode ID1 to temporarily cease broadcasting during the first timeinterval. Here, this second subgroup cluster of ID nodes ID7-ID16includes a larger number of nodes and may be selected by the server87100 given the server 87100 has determined the location of such IDnodes ID7-ID16 are a greater distance from target ID node ID1 than thefirst subgroup cluster of nodes. This second subgroup cluster of IDnodes ID7-ID16 may have also been selected by the server 87100 basedupon their respective presently broadcasting power levels and/orfrequencies.

In more detail, an embodiment may have the server 87100 identifydifferent subgroup clusters of nodes from this type of initial group ofother node proximate to the target node based upon a clusteringparameter (such as power levels and/or frequencies used). Such aclustering parameter, for example, may also include shipping informationstored on the server and related to each other nodes in the initialgroup. In this manner, one subgroup cluster of nodes (e.g., ID nodesID7-ID16) may be clustered or grouped for purposes of pruning given theycollectively are to be delivered to one or more locations near thedelivery vehicle storage area 87210 while another subgroup cluster ofnodes (e.g., ID nodes ID2-ID16) may be associated or paired withpackages that are indicated, via relevant shipping information stored onserver 87100, to be staying in storage location A 87205 while the firstsubgroup cluster of nodes will be moving on.

In another example, the clustering parameter used by server 87100 mayinclude context data stored on the server. As explained above in moredetail, context data (such as context data 560) relates to ananticipated environment for a node, such as data related to structures(e.g., layout information, data on buildings, machinery, containers withshielding properties, etc.) near the node that may affect communicationto and from the node. Thus, such context data that may be used by server87100 as a type of clustering parameter may include information for eachnode in the initial group of nodes proximate the target node duringpredicted movement of each node in the group.

In still another example, the clustering parameter used by server 87100may include association data stored on the server. Consistent with whatis described above relative to exemplary association data 540, suchassociation data that may be used by server 87100 as a type ofclustering parameter identifying server-permitted relationships betweendifferent ones of the nodes in the initial group of nodes proximate thetarget node. For example, ID nodes ID2-ID6 may be associated with targetID node ID1, which may receive sensor data from each of ID nodesID2-ID6. By identifying the subgroup cluster of nodes ID2-ID6 based ontheir respective associations to target ID node ID1, the server 87100may allow ID nodes ID2-ID6 to continue detecting using onboard sensorsbut to temporarily cease communications, while allowing the target IDnode ID1 that has already gathered the sensor data from those other IDnodes ID2-ID6 to better communicate back to master node 87110 a withoutthe interference from nodes ID2-ID6. This type of dynamic and selectiveuse of different kinds of clustering parameters provides the server87100 with a robust set of tools with which to deploy in an embodimentwhen managing a highly congested node landscape.

When the first time interval elapses, the nodes (e.g., master nodes, IDnodes, or both) that were temporarily caused by server 87100 to ceasebroadcasting may revert back to a normal broadcasting mode per theirindividual and respective broadcast profiles. At this point, anembodiment of the server 87100 may recheck or update the operating nodedensity relative to the previously identified target node to determineif further enhanced communication controls are desired relative to thattarget node with further or different pruning and/or clustering forpruning.

For example, many of the nodes may not have moved after the first timeinterval elapsed. As such, if server 87100 updates the operating nodedensity relative to target ID node ID1 and that density still exceedsthe threshold, server 87100 may cause the second subgroup cluster of IDnodes ID7-16 (as shown in FIG. 87D) to temporarily cease broadcasting ina second time interval rather than cause the same subgroup cluster of IDnodes ID2-ID6 (as shown in FIG. 87C) to again cease broadcasting duringthe first time interval.

However, in another example, some of the nodes may have moved during thefirst time interval. For instance, some of the nodes may have been movedwith their respective packages from the storage location A 87205 to thedelivery vehicle storage area 87210 during the first time interval. Assuch and as shown in FIG. 88A, ID nodes ID7-ID16 and ID19-ID21 may be indifferent locations after the first time interval expires when comparedto their respective positions as shown in FIG. 87A. In this new nodelandscape configuration, target ID node ID1 is operating with adifferent proximate operating node density environment and server 87100may revisit how it may be managing communications with target ID nodeID1 using an updated operating node density near the location of thetarget node and re-clustering for additional pruning techniques that maycause different neighboring nodes to temporarily cease broadcastingduring a time interval after the first time interval expired.

In more detail, server 87100 may be further operative to determine,after the first time interval expires, an updated operating node densityof an updated group of other nodes proximate to the current location ofthe target node ID1. For example, as shown in FIG. 88B, server 87100 maydetermine that an updated operating node density relative to target nodeID1 is 5, which corresponds to the group of ID nodes ID2-ID6 proximateto the location of target node ID1. In the example shown in FIG. 88B,the updated operating node density is 5, which does not exceed the valueof the operating node density threshold in this example. Thus, server87100 need not prune any of the neighboring nodes near target ID nodeID1. However, if server 87100 did find the updated operating nodedensity exceeds the threshold once the first time interval expires,server 87100 may transmit a further change in the broadcast profile toat least one of ID nodes ID2-ID6. Such a further change in the broadcastprofile would cause that ID node from the updated group of ID nodesID2-ID6 to temporarily cease broadcasting during a second subsequenttime interval. Thus, server 87100 is able to actively managecommunications with target ID node ID1 in such a dynamically changingnode landscape.

While target node ID1, as shown in FIG. 88B, appears stationary relativeto its initial position shown in FIG. 87A, those skilled in the art willappreciate that the target node may be mobile and have a differentupdated location at the end of the first time interval compared to whereit was located at the beginning of the first time interval. Suchmovement may have the target node located proximate an entirelydifferent set of nodes compared to where it was at the beginning of thefirst time interval. In other words, the updated group of other nodesnear the target node may be different in composition compared to theinitial group of other nodes near the target node due to the targetnode's own movement during the first time interval.

Similar to that shown in FIG. 87D, server 87100 may use a subgroupcluster of nodes out of the updated group of node proximate to theupdated location of the target node. As such, the server 87100 may befurther operative to identify updated subgroup clusters of nodes fromthe updated group of other nodes proximate to the updated location ofthe target node, and then transmit the further change in the broadcastprofile to each node in a first of the updated subgroup clusters ofnodes if the updated operating node density exceeds the threshold afterthe first time interval expires. Such a further change in the broadcastprofile causes each node in that first updated subgroup cluster of nodesto temporarily cease broadcasting during the second time interval. Thus,a similar subgroup clustering technique may be deployed after the firsttime interval expires and there remains a need to prune via updatedsubgroup clusters of neighboring nodes

Further changes in broadcast profiles may also be made by the server87100 after the second time interval expires. For example, server 87100may transmit a further change in the broadcast profile to each node in asecond of the updated subgroup clusters of nodes near the target nodeafter the second time interval expires when the updated operating nodedensity still exceeds the threshold. This further change in thebroadcast profile transmitted to each node in the second of the updatedsubgroup clusters of nodes causes a temporary cease of broadcasting foreach node in the second of the updated subgroup clusters of nodes duringa third time interval.

In FIG. 89A, the nodes ID1-ID21 within the illustrated logistics nodenetwork are shown in a later configuration. Here, various nodes andtheir associated items/packages have moved from the delivery vehiclestorage area 87210 and then into an exemplary delivery vehicle 89000. Inparticular, ID nodes ID7-ID16 are shown as having been moved intodelivery vehicle 89000, but communications to and from some of those IDnodes may be hampered due to the potential for a congested operatingnode environment within the delivery vehicle 89000. As such, server87100 may take steps to manage communications related to the ID nodeswithin the delivery vehicle 89000.

For example, in the embodiment shown in FIG. 89A, server 87100 mayidentify ID node ID13 as another target node located within thecommunication range of master node 87110 b (or within the communicationrange of a vehicle master node (not shown) within delivery vehicle89000). Similar to the example explained above relative to target IDnode ID1 in FIGS. 87A-D, server 87100 may identify that new target nodeID node ID13 is surrounded by the group of ID nodes ID7-ID12, ID14-ID16proximate to the location of ID node ID13 within the delivery vehicle89000.

Next, server 87100 determines the operating node density of this groupof ID nodes relative to ID node ID13 as compared to to a threshold nodedensity value (such as 5). In the example of FIG. 89A, server 87100 maydetermine that within a certain distance range relative to target IDnode ID13 the operating node density is currently 9 operating nodes forthose that fall within that range (i.e., the group of ID nodes ID7-ID12and ID14-ID16 disposed and located within the delivery vehicle 89000).Accordingly, server 87100 identifies that target node ID13 is currentlyin an overly congested node environment given the determined operatingnode density exceeds the threshold of 5. As a result, the server 87100is then operative to transmit a change in a broadcast profile to atleast one neighboring node from the group of ID nodes ID7-ID12 andID14-ID16 proximate to the location of the target node ID13 withindelivery vehicle 89000. For example, as shown in FIG. 89B, exemplaryserver 87100 may cause a selected subgroup cluster of ID nodes ID10,ID12, and ID14-ID16 to change their respective broadcast profiles sothat each of these ID nodes temporarily ceases broadcasting duringanother time interval.

Those skilled in the art will appreciate that the selection of one ormore of neighboring nodes of target ID node ID13 within delivery vehicle89000 to be those that are caused to temporarily cease broadcasting maybe implemented similar to and consistent with the example explainedabove relative to target ID node ID1. Thus, such neighboring nodes thatare pruned to temporarily cease broadcasting for a time interval mayinclude a single node during the time interval, multiple nodes as asubgroup cluster during the time interval, multiple nodes thatincrementally change their respective broadcasting profile during thetime interval, or all nodes within a specific range of the target nodeduring the time interval.

Those skilled in the art will also appreciate that while contemplateddeployment of such unconventional communication management techniques ina logistics environment may involve much larger numbers of logisticsrelated nodes at different levels of the logistics network (includingboth low level ID nodes and higher level master node) and higheroperating node density situations, the example embodiments shown inFIGS. 87A-89B are simplified for ease of discussion and clarity.

In the embodiments shown in FIGS. 87A-89B, exemplary server 87100 is amanaging type of component of a logistics network that implementsenhanced communication management for congested node environments. FIG.90 is a diagram illustrating further details of exemplary server 87100in accordance with an embodiment of the invention that uses high densitynode communication management code 90000 as part of server control andmanagement code 90525 to implement such enhanced communicationmanagement functionality in an unconventional manner. Referring now toFIG. 90, exemplary server 87100 is shown similar to server 100 (whichwas earlier described relative to FIG. 5). More specifically, thoseskilled in the art will appreciate that one embodiment of exemplaryserver 87100 includes many of the same hardware, code, and datacomponents as shown for exemplary server 100 of FIG. 5. As such, similarfunctionality exists for what is numbered the same or similarly anddescribed above regarding exemplary server 100. Thus, while server 100shown in FIG. 5 is described as having processing unit 500, userinterface 505, memory storage 515, volatile memory 520, context database565, network interface 590, and medium/long range communicationinterface 595, those skilled in the art will appreciate that exemplaryserver 87100 may use similar hardware components as shown in FIG. 5.This includes at least processing unit 90500, user interface 90505,memory storage 90515, volatile memory 90520, context database 90565,network interface 90590, and medium/long range communication interface90595.

Further, the embodiment of exemplary server 87100 illustrated indetailed FIG. 90 deploys high density node communication management code90000, which is stored in memory storage 90515 as part of server controland management code 90525. High density node communication managementcode 90000 may be loaded into volatile memory 90505 for execution byprocessing unit 90500. The server control and management code 525, aspreviously described, generally controls the behavior of the serverrelating to communications (with a node advertise and query logicmanager), information management (with an information control andexchange manager), power management (with a node power manager thatinteracts with the various communication interfaces, for example, tomanage power consumption and broadcast power aspects at a low level),and association management (with an association manager). As such,server control and management code 90525 essentially operates similar tothat as described above for server node control and management code 525but further includes high density node communication management code90000 for functions used to provide enhanced communication management ofwireless nodes operating in a congested logistics node networkenvironment as described in FIGS. 87A-89B above and as described in moredetail below with respect to the methods described relative to FIGS. 91and 92. Thus, an embodiment of high density node communicationmanagement code 90000 may be implemented as an integrated part of servercontrol and management code 90525, such as one or more programmaticfunctions or additional program modules that may be called within code90525. However, in other embodiments, the high density nodecommunication management code 90000 used to implement the method asdescribed with respect to FIGS. 87A-89B, 91, and 92 may be implementedseparately from code 90525 in a way that allows code 90000 to call someof the programmatic functions or program modules described as part ofcode 525 (or 90525) to implement the steps as laid out in the methodsillustrated by FIGS. 91-92 and variations of those methods as describedherein.

In general, exemplary high density node communication management code90000 programmatically adapts and transforms the operation of server87100 such that server 87100 unconventionally functions to generallyidentify a target node; determine an operating node density relative tothat target node based upon locations known or determined by the serverof the target node and other neighboring nodes; and cause one or more ofthe neighboring nodes to temporarily cease broadcasting for a particulartime interval via transmitted changes to those nodes' broadcastprofiles. In some embodiments, the transmitted change may be implementedwith a command to simply temporarily cease broadcasting for the timeinterval. This may have the receiving node altering the currentparameters of its broadcasting profile. However, in other embodiments,the transmitted change may take the form of a server instruction for theparticular neighboring node to use a different broadcast profile for aset period of time. In some instances, such an instruction may also havethe particular neighboring node revert back to the original broadcastprofile after the set period of time ends. Those skilled in the art willappreciate that the availability of multiple different broadcastprofiles to use allows for a proactive selection of a desiredcommunication profile to fit with a particular type of node operatingenvironment or instructions received from the server regarding changedcommunication related operations for the node.

FIG. 91 is a flow diagram illustrating an exemplary enhanced method ofcommunication management of a plurality of wireless nodes by a serveroperating in a wireless node network in accordance with an embodiment ofthe invention. Exemplary method 9100 generally focuses onserver-implemented steps that collectively amount to unconventionalserver functionality that has the technical effect of enhancingcommunication management relative to a particular target node within thewireless node network. Stated another way, exemplary method 9100generally focuses on a collection of steps performed by a server (suchas server 87100) that addresses a congested logistics network issue withunconventional server functionality that improves the communicationoperations of the target node within the wireless node network.

Referring now to FIG. 91, exemplary method 9100 begins at step 9105 withthe server identifying a target node from multiple nodes (master nodesor ID nodes) within the wireless node network. As explained in theexamples shown in FIG. 87A-87D, server 87100 identifies the target nodeas ID node ID1 deployed at a lower level of the network and associatedwith an item/package being shipped or transported. However in anotherembodiment, server 87100 may have identified the target node as masternode 87110 a at a middle level of the network.

At step 9110, method 9100 proceeds with the server locating an initialgroup of other nodes proximate to the initial location of the targetnode. Thus, in the example shown in FIG. 87B, server 87100 may determinethe location of ID nodes ID2-ID16 as being in an initial group of othernodes within a particular range that is proximate to the initiallocation of target node ID1.

At step 9115, method 9100 proceeds with the server determining anoperating node density (OND) of the identified initial group of othernodes proximate to the initial location of the target node. For example,for the initial group of ID nodes ID2-ID16 proximate ID node ID1, server87100 would determine this initial group of nodes has an operating nodedensity of 15. At step 9120, method 9100 checks to see if the determinedoperating node density is greater than a threshold value for theoperating node density. If so, then step 9120 proceeds to step 9125.Otherwise, there is no need to have the server take furthercommunication management actions related to the identified target nodeand step 9120 proceeds to the end of method 9100. For example, in theembodiment shown and explained relative to FIG. 87B, server 87100determines that the current operating node density for target node ID1(15) exceeds the threshold value set for the operating node density (5),so further communication management actions by server 87100 arewarranted relative to target node ID1 and method 9100 proceeds from step9120 to step 9125.

At step 9125, method 9100 has the server identifying at least oneneighboring node from the initial group of other nodes proximate to thetarget node's initial location. In one embodiment, the neighboring nodecomprises a single node from those within the initial group of othernodes. Such a single node may be located closer to the target nodecompared to at least a majority of the remaining nodes in the initialgroup of other nodes. For example, as shown in FIG. 87B, server 87100may identify ID node ID2 (which may be paired with a package) as theneighboring node that will be temporarily pruned to cease broadcastingfor a time (as explained in more detail below).

In another embodiment, the at least one neighboring node identified instep 9125 may be a subgroup cluster of nodes from the initial group ofother nodes proximate to the initial location of the target node. Forexample, as shown in FIG. 87C, server 87100 may identify ID nodesID2-ID6 as the neighboring nodes that will be temporarily pruned tocease broadcasting for a time (as explained in more detail below) inorder to effect easier communication to and from target ID node ID1.

When “clustering” or identifying subgroup clusters of nodes from theinitial group of nodes proximate the target node's location, a furtherembodiment may have the server identifying such subgroup clusters ofnodes using a clustering parameter that distinguishes different nodeswithin the initial group. For example, a clustering parameter may beshipping information stored on the server and related to each node inthe initial group of other nodes. Using such shipping information as aclustering parameter, the server may identify one subgroup cluster ofnodes from the initial group as including those nodes having a firstcommon destination address or location for delivery or transfer, whileidentifying another subgroup cluster of nodes from the initial group asincluding those nodes having a second destination address or locationfor delivery or transfer.

In another example, the clustering parameter may involve context datastored on the server and relating to an anticipated environment for eachnode in the initial group of other nodes during predicted movement ofeach node in the group of other nodes. Using context data as theclustering parameter, the server may identify one subgroup cluster ofnodes from the initial group as including those nodes currently movingon a conveyor system (such as conveyor system 87200), while identifyinganother subgroup cluster of nodes from the initial group as includingthose nodes within a building (such as nodes still located withinstorage location A 87205).

In still another example, the clustering parameter may involveassociation data stored on the server where the association dataidentifies server-permitted logical relationships between different onesof the nodes in the initial group of other nodes. Using association dataas the clustering parameter, the server may identify one subgroupcluster of nodes from the initial group as including those nodescurrently associated with one master node, while identifying anothersubgroup cluster of nodes from the initial group as including thosenodes current associated within another master node in close proximityto the target node.

At step 9130, method 9100 has the server transmitting a change in abroadcast profile to the identified neighboring node(s) from the initialgroup given the operating node density exceeds the threshold. Thischange in the broadcast profile causes the neighboring node(s) totemporarily cease broadcasting during a first time interval. Thus, thisserver initiated proactive operation changes the electroniccommunication landscape for the target node so to improve thecommunication operations of the target node in an unconventional manner.

When the neighboring node(s) are identified as a subgroup cluster ofnodes, a further embodiment of step 9130 may have the servertransmitting the change in the broadcast profile to each node in thesubgroup cluster of nodes given the operating node density exceeds thethreshold. This change in the broadcast profile causes each node in thesubgroup cluster of nodes to temporarily cease broadcasting during thefirst time interval.

In an embodiment that uses multiple subgroup clusters of nodes, anotherfurther embodiment of step 9130 may be implemented by identifying aplurality of subgroup clusters of nodes from the initial group of othernodes as the at least one neighboring node, and then having the servertransmitting the change in the broadcast profile to each node in one ormore of the subgroup clusters of nodes if the operating node densityexceeds the threshold. Such a change in the broadcast profile causeseach node in those different subgroup clusters of nodes to temporarilycease broadcasting during the first time interval.

At step 9135, method 9100 has the server waiting until the end of thefirst time interval. During this time, the changes transmitted to theappropriate neighboring nodes in step 9130 have those nodes ceasingtheir broadcasting activity so that the target node can more effectivelycommunicate in such a congested environment. But once the first timeinterval ends or expires, step 9135 proceeds to step 9140.

At step 9140, method 9100 proceeds to have the server determine anupdated operating node density (UOND) of an updated group of other nodesin the plurality of wireless nodes proximate to an updated location ofthe target node. At this point in time, some of the nodes in thelogistics-related node network may have moved—including the target node.This dynamic aspect of such a logistics-related node network with mobilenodes causes the operational node landscape to change over time. As aresult, the updated location of the target node may be different whencompared to the initial location (i.e., the location in step 9105).Furthermore, given movement of the nodes, the updated group of othernodes may be different compared to the initial group of other nodes nearthe target node as previously located in step 9110.

If the server determines in step 9145 that the updated operating nodedensity (UOND) for the target node at its updated location is greaterthan the threshold, then the target node is still deemed to be in acongested node landscape where server-based communication managementactions may be warranted to help locally reduce potential communicationinterference from neighboring nodes. Thus, if the UOND is greater thanthe threshold, step 9145 proceeds to step 9150. Otherwise, if the UONDis not greater than the threshold, the server may permit normalcommunications to occur with the regular broadcast profile settings asthey are with the neighboring nodes proximate the target node.

At step 9150, method 9100 proceeds with the server identifying at leastone neighboring node from the updated group of the other nodes within aproximate range of the target node's updated location, and then in step9155 has the server transmitting a further change in the broadcastprofile to at least one node from the updated group of other nodesproximate to the updated location of the target node given the updatedoperating node density exceeds the threshold. This further change in thebroadcast profile causes the at least one node from the updated group ofother nodes to temporarily cease broadcasting during a second timeinterval. Such a neighboring node or nodes from the updated group may bejust one node near the target node or a subgroup cluster of multiplenodes near the target node. Further still, the neighboring nodes causedto temporarily cease broadcasting during the second time interval may bea second subgroup cluster of nodes (distinct from or not having all ofthe same nodes as the first subgroup cluster of nodes that where causedto temporarily cease broadcasting during the first time interval).

In still another further embodiment of method 9100, the server mayidentify multiple updated subgroup clusters of nodes from the updatedgroup of other nodes proximate to the updated location of the targetnode once the first time interval expires as part of step 9150. As such,a further embodiment of step 9155 may have the server transmitting thefurther change in the broadcast profile to each node in a first of theupdated subgroup clusters of nodes (to cause each node in the first ofthe updated subgroup clusters of nodes to temporarily cease broadcastingduring the second time interval). Alternatively, the server may transmitthe further change in the broadcast profile to the first of the updatedsubgroup clusters during one part of the second time interval and thentransmit the further change in broadcast profile to a second of theupdated subgroup clusters during another part of the second timeinterval (e.g., another non-overlapping part of the second time intervalor another partially overlapping part of the second time interval).Similar clustering parameters may be used by the server when identifyingsuch updated neighboring nodes—whether single nodes, a subgroup cluster,or multiple subgroup clusters. Likewise, similar updating of operatingnode density relative to a target node may be performed by the serverafter the second time interval expires and similar pruning/clusteringcommunication management techniques may be enacted by the server instill a third or subsequent time interval as needed to help proactivelycreate an improved node landscape relative to the target node's locationso that the target node may communicate more effectively without undueinterference.

Those skilled in the art will appreciate that method 9100 as disclosedand explained above in various embodiments may be implemented on aserver apparatus, such as server 87100 illustrated in FIGS. 87A-90,running one or more parts of server control and management code 90525(i.e., the high density node communication management code 90000). Suchcode may be stored on a non-transitory computer-readable medium such asmemory storage 90515 on server 87100. Thus, when executing code 90525(that is implemented to include such high density node communicationmanagement code 90000), the server's processing unit 90500 may becomeunconventionally operative to perform operations or steps from theexemplary methods disclosed above, including method 9100 and variationsof that method.

While method 9100 and its variations as described above focus onunconventional operations of a server as it enhances communicationmanagement for target nodes in a wireless node network, a further methodmay focus on more detailed operations of both the server and the targetnode's neighboring nodes as they collectively provide enhancedcommunication management as a system to address an overly congested nodeoperating environment. FIGS. 92A-92B are collectively a flow diagramillustrating another exemplary enhanced method of communicationmanagement of a plurality of wireless nodes by a server and a targetnode's neighboring node(s) as they interact within a wireless nodenetwork in accordance with an embodiment of the invention.

In general, method 9200 includes specific steps performed by a server(similar to that shown and described above relative to method 9100 andits variations), but also includes detailed steps performed by theidentified neighboring node(s) that are near the target node (e.g.,steps 9235, 9240, 9250, 9275, and 9280). In more detail and referringnow to FIG. 92A, exemplary method 9200 begins at step 9205 with theserver identifying the target node from the plurality of wireless nodesin a logistics-related wireless node network (such as that shown in FIG.87A). In this step, the target node is at an initial location, such aslocated in a storage location. The target node may be identified as amaster node capable of separately communicating with the server over afirst communication path and communicating with at least a portion ofthe network's wireless nodes over a second communication path (such ascommunicating with ID nodes that each are paired with differentpackages).

At step 9210, method 9200 proceeds with the server identifying andlocating an initial group of other nodes that are within a predetermineddistance from the initial location of the target node. Thus, in theexample shown in FIG. 87B, server 87100 may determine the location of IDnodes ID2-ID16 as being in an initial group of other nodes within aparticular distance from the initial location of target node ID1. Eachof ID nodes ID2-ID16 may be ID nodes that are attached to, associatedwith, or otherwise paired with different packages.

At step 9215, method 9200 proceeds with the server determining anoperating node density (OND) of the identified initial group of othernodes before proceeding to step 9220. If the determined operating nodedensity is not greater than a threshold value, method 9200 concludesgiven the identified target node is able to communicate effectively withan operating node density at a sufficiently low level to permit suchcommunication without interference from other surrounding nodes.However, if the determined operating node density is greater than athreshold value, step 9220 proceeds to step 9225.

At step 9225, method 9200 has the server identifying at least oneneighboring node from the initial group of other nodes within theparticular distance from the target node's initial location. Aspreviously explained, such a neighboring node relative to a target nodemay be identified as one node, a group of several nodes (a subgroupcluster), or multiple groups of several nodes (multiple subgroupclusters) from those other nodes within the initial group near thetarget node. Stated another way, in one embodiment, a neighboring nodemay be identified in step 9225 as a single node in the initial group(such as an ID node paired with a package) that is located closer to thetarget node compared to at least a majority of the remaining nodes inthe initial group. In another embodiment, the neighboring nodeidentified in step 9225 may be one or more subgroup clusters of multiplenodes from the initial group of other nodes.

When identifying the neighboring nodes in step 9225, the server may relyupon a clustering parameter when identifying and categorizing some ofthe nodes in the initial group into the one or more subgroup cluster ofnodes used as neighboring nodes for purposes of pruning to aidcommunication to and from the target node. For example and as explainedin more detail above, the clustering parameter used by the server may beinformation stored on the server, such as shipping information relatedto each node in the initial group, context data related to ananticipated environment for each node in the initial group of othernodes during predicted movement of each node in the group of othernodes, or association data identifying server-permitted relationshipsbetween different nodes in the initial group.

With the one or more neighboring nodes identified in step 9225, method9200 proceeds to step 9230 where the server transmits a broadcastprofile change message to the identified neighboring node(s) from theinitial group given the operating node density exceeds the threshold.Thus, when the neighboring node is a subgroup cluster of nodes, theserver transmits the broadcast profile change message to each node inthe subgroup cluster of nodes as part of step 9230. As explained insteps 9235 and 9240 in more detail, the transmitted broadcast profilechange message causing each node in the subgroup cluster of nodes totemporarily cease broadcasting during the first time interval. In afurther embodiment when the server identifies multiple subgroup clustersfrom nodes as potential neighboring nodes, the server may transmit thebroadcast profile change message to each node in a first of the subgroupclusters of nodes, given the operating node density exceeds thethreshold, to cause each node in the first of the subgroup clusters ofnodes to temporarily cease broadcasting during the first time interval.In another further embodiment, the server may transmit the broadcastprofile change message to each node in a second of the subgroup clustersof nodes after the first time interval expires and if the operating nodedensity still exceeds the threshold. The broadcast profile changemessage transmitted to each node in the second subgroup clusters ofnodes causes a temporary cease of broadcasting for each node in thesecond subgroup clusters of nodes during a second time interval.

At step 9235, method 9200 has the identified neighboring node(s)receiving the broadcast profile change message from the server. If theidentified neighboring node is a master node, that master node maydirectly receive the broadcast profile change message from the server.However, when the identified neighboring node is an ID node (such as apackage ID node paired with a package or item being shipped), that IDnode may indirectly receive the broadcast profile change message fromthe server using an intermediary master node at a mid-level of thewireless node network.

At step 9240, method 9200 has the identified neighboring node(s)changing a broadcast profile resident and operating on that wirelessnode to a temporary silent mode. Such a temporary silent mode causesthat neighboring node to temporarily cease broadcasting during a firsttime interval. When the first time interval expires, method 9200proceeds from step 9245 through transition A to step 9250 in FIG. 92B.Referring now to FIG. 92B at step 9250, method 9200 proceeds with theidentified neighboring node(s) resetting their respective broadcastprofile to a previous broadcast mode in order to no longer preventnode(s) from broadcasting.

At step 9255, method 9200 proceeds with the server determining anupdated operating node density (UOND) of an updated group of other nodesin the plurality of wireless nodes that are within the predetermineddistance from an updated location of the target node. Such an updatedlocation of the target node may be different compared to the targetnode's initial location if the target node has moved during the firsttime interval. Likewise, those skilled in the art will appreciate thatthe updated group of other nodes is different compared to the initialgroup of other nodes due to node movement. Thus, the updated operatingnode density related to the target node reflects a potentially changedoperating node landscape for the target node.

At step 9260, method 9200 has the server determining if the updatedoperating node density is greater than the threshold value. If thedetermined updated operating node density is not greater than thethreshold value, step 9260 moves to the end of method 9200 as the targetnode now no longer needs server-based enhanced communication managementassistance in order to sufficiently communicate with other nodes.However, if the determined updated operating node density is greaterthan the threshold value, step 9260 proceeds to step 9265.

At step 9265, method 9200 has the server identifying at least a secondneighboring node or neighboring nodes to the target node from theupdated group of other nodes and then transmitting a further broadcastprofile change message to the identified second neighboring node(s) instep 9270. At step 9275, method 9200 has the identified secondneighboring node(s) receiving the broadcast profile change message fromthe server. Then, at step 9280, method 9200 has the identified secondneighboring node(s) changing a broadcast profile resident and operatingon the identified neighboring node(s) to the temporary silent mode thatcauses such nodes to temporarily cease broadcasting during a second timeinterval.

In a further embodiment of method 9200, step 9265 may have the serveridentifying multiple updated subgroup clusters of nodes from the updatedgroup of other nodes in the plurality of wireless nodes that are withinthe predetermined distance from an updated location of the target node.With these identified multiple updated subgroup clusters of nodes aspotential neighboring nodes that may be temporarily silenced, the servermay transmit the further broadcast profile change message to each nodein a first of the updated subgroup clusters of nodes given the updatedoperating node density exceeds the threshold after the first timeinterval expires. This further broadcast profile change message causeseach node in this first updated subgroup clusters of nodes totemporarily cease broadcasting during the second time interval.

Thereafter, the server may also transmit the further broadcast profilechange message to each node in a second of the updated subgroup clustersof nodes after the second time interval expires and if the updatedoperating node density still exceeds the threshold. At this point, thefurther broadcast profile change message transmitted by the server toeach node in the second of the updated subgroup clusters of nodes causesa temporary cease of broadcasting for each node in the second of theupdated subgroup clusters of nodes during a third time interval. Assuch, the server and the nodes operating as neighboring nodes relativeto the target node may function as a type of system that enhances howthe target node can communicate with other elements of a wireless nodenetwork.

While a server, such as server 87100) as shown and explained relative toFIGS. 87A-92B, may be deployed in different embodiments that provideenhanced communication management relative to a target node in awireless node network in order to improve target node communicationoperations in a congested node environment, further embodiments maydeploy a specially programmed master node (i.e., a communicationmanagement master node) for this type of role within the logisticsrelated wireless node network. In general, an exemplary communicationmanagement master node, as modified with programming to provide enhancedcommunication management functionality, may be deployed at a layer ofthe network below the server and rely on node management rule dataprovided by the server when interacting with neighboring nodes of atarget node. Such node management rule data (such as a whitelist type ofdata structure) helps to identify which other lower level nodes withinthe network fall within the control of that particular master node. FIG.93 is a diagram illustrating details of an exemplary modified masternode that uses one or more node management rules to provide enhancedcommunication management for a congested node environment in accordancewith an embodiment of the invention.

Referring now to FIG. 93, exemplary communication management master node93110 a is illustrated in accordance with an embodiment of the inventionthat uses high density node communication management code 93000 as partof master control and management code 93425 to implement such enhancedcommunication management functionality in an unconventional manner.Those skilled in the art will appreciate that exemplary master node93110 a is shown similar to master node 425 (previously describedrelative to FIG. 4) as well as master nodes 87110 a and 87110 b(previously described as deployed in the embodiments shown in FIGS.87A-89B). More specifically, those skilled in the art will appreciatethat an embodiment of exemplary master node 93110 a includes many of thesame hardware, code, and data components as shown for exemplary masternode 425 (as well as master nodes 87110 a, 87110 b). As such, similarfunctionality exists for what is numbered the same or similarly anddescribed above regarding exemplary master node 425. Thus, while masternode 425 shown in FIG. 4 is described as having processing unit 400,memory storage 415, volatile memory 420, clock/timer 460, sensors 465,battery/power interface 470, GPS 475, short range communicationinterface 480, and medium/long range communication interface 485, thoseskilled in the art will appreciate that exemplary master node 93110 amay use similar hardware components as shown in FIG. 4. This includes atleast processing unit 93400, memory storage 93415, volatile memory93420, clock/timer 93460, sensors 93465, battery/power interface 93470,GPS 93475, short range communication interface 93480, and medium/longrange communication interface 93485.

Further, the embodiment of exemplary communication management masternode 93110 a illustrated in detailed FIG. 93 deploys high density nodecommunication management code 93000, which is stored in memory storage93415 as part of master control and management code 93425. High densitynode communication management code 93000 may be loaded into volatilememory 93420 for execution by processing unit 93400. The master controland management code 425, as previously described, generally controls thebehavior of the master node relating to communications (with a nodeadvertise and query logic manager), information management (with aninformation control and exchange manager), power management (with a nodepower manager that interacts with the various communication interfaces,for example, to manage power consumption and broadcast power aspects ata low level), association management (with an association manager), andlocation determination functionality (with a location aware/capturemodule). As such, master control and management code 93425 essentiallyoperates similar to that as described above for master node control andmanagement code 425 but further includes high density node communicationmanagement code 93000 for functions used to provide enhancedcommunication management of wireless nodes operating in a congestedlogistics node network environment as described in FIGS. 87A-89B and inmore detail below with respect to the methods described relative to FIG.94. Thus, an embodiment of high density node communication managementcode 93000 may be implemented as an integrated part of master controland management code 93425, such as one or more programmatic functions oradditional program modules that may be called within code 93425.However, in other embodiments, the high density node communicationmanagement code 93000 used to implement the method as described withrespect to FIGS. 87A-89B, and 94 may be implemented separately from code93425 in a way that allows code 93000 to call some of the programmaticfunctions or program modules described as part of code 425 (or 93425) toimplement the steps as laid out in the method illustrated by FIG. 94 andvariations of that method as described herein.

In general, exemplary high density node communication management code93000 programmatically adapts and transforms the operation of exemplarycommunications management master node 93110 a such that master node93110 a unconventionally functions to generally identify a target nodeusing a node management rule 93005 provided by a server (such as server87100); determine an operating node density relative to that target nodebased upon locations known or determined by the server of the targetnode and other neighboring nodes; and cause one or more of theneighboring nodes to temporarily cease broadcasting for a particulartime interval via transmitted changes to those nodes' broadcastprofiles. In some embodiments, the transmitted change may be implementedwith a command to simply temporarily cease broadcasting for the timeinterval. This may have the receiving node altering the currentparameters of its broadcasting profile. However, in other embodiments,the transmitted change may take the form of a master node instructionfor the particular neighboring node to use a different broadcast profilefor a set period of time. In some instances, such an instruction mayalso have the particular neighboring node revert back to the originalbroadcast profile after the set period of time ends. Those skilled inthe art will appreciate that the availability of multiple differentbroadcast profiles to use allows for a proactive selection of a desiredcommunication profile to fit with a particular type of node operatingenvironment or instructions received from the server regarding changedcommunication related operations for the node.

As noted above, the exemplary communication management master node 93110a may identify the target node from a subset of the wireless nodeswithin the logistics-related wireless node network. This subset ofwireless nodes is defined by node management rule 93005, which isinitially received from the server and stored within the master node asa type of association data (e.g., association data 93440 similar to thatgenerally described above as association data 440). An embodiment ofcommunication management master node 93110 a may receive an initialinstance of node management rule 93005, but may also receive an updatefor the node management rule from the server. Such an updated nodemanagement rule defines an alternative subset of the wireless nodesassigned to the master node for communication management. This may occurperiodically given the dynamic nature of movement of the nodes withinthe logistics-related wireless node network. For example, thecommunication management master node 93110 a may receive an update fornode management rule 93005 after a time interval expires where themaster node has caused certain neighboring nodes near a target node totemporarily cease broadcasting.

FIG. 94 is a flow diagram illustrating an exemplary enhanced method ofcommunication management of a plurality of wireless nodes by acommunication management master node, such as master node 93110 a,operating in a wireless node network in accordance with an embodiment ofthe invention. Exemplary method 9400 generally focuses on masternode-implemented steps that collectively amount to unconventional masternode functionality from a mid-level of the network that has thetechnical effect of enhancing communication management relative to aparticular target node within the wireless node network. Stated anotherway, exemplary method 9400 generally focuses on a collection of stepsperformed by a specially programmed master node (such as master node93110 a) that addresses a congested logistics network issue withunconventional functionality that leverages a node management ruleprovided by a server in the network as part of improving thecommunication operations of the target node within the wireless nodenetwork. Thus, method 9400 generally describes master node operationsthat interact with a server and other nodes in the network to enhancecommunication management via similar pruning techniques as describedabove relative to a target node and neighboring node(s).

Referring now to FIG. 94, exemplary method 9400 begins at step 9405 withan exemplary communication management master node identifying a targetnode from a subset of the wireless nodes (master nodes and/or ID nodes)where the subset is defined by a node management rule (such as nodemanagement rule 93005) received from a server and stored within themaster node. The identified target node is currently at an initiallocation. For example, as shown in FIG. 87A-87D, master node 87110 a maybe modified as a communication management master node 93110 a to usehigh density node communication management code 9300 and node managementrule data 93005 to identify the target node as ID node ID1 deployed at alower level of the network and associated with an item/package beingshipped or transported.

At step 9410, method 9400 proceeds with the server locating an initialgroup of other nodes proximate to the initial location of the targetnode. Thus, in the example shown in FIG. 87B, master node 87110 a(modified to be implemented as master node 93110 a) may determine thelocation of ID nodes ID2-ID16 as being in an initial group of othernodes within a particular range that is proximate to the initiallocation of target node ID1.

At step 9415, method 9400 proceeds with the master node determining anoperating node density (OND) of the identified initial group of othernodes proximate to the initial location of the target node. For example,for the initial group of ID nodes ID2-ID16 proximate ID node ID1, masternode 87110 a (modified to be implemented as master node 93110 a) woulddetermine this initial group of nodes has an operating node density of15. At step 9420, method 9400 checks to see if the determined operatingnode density is greater than a threshold value for the operating nodedensity. If so, then step 9420 proceeds to step 9425. Otherwise, thereis no need to have the master node take further communication managementactions related to the identified target node and step 9420 proceeds tothe end of method 9400. For example, in the embodiment shown andexplained relative to FIG. 87B, master node 87110 a (modified to beimplemented as master node 93110 a) determines that the currentoperating node density for target node ID (15) exceeds the thresholdvalue set for the operating node density (5), so further communicationmanagement actions by master node 87110 a (modified to be implemented asmaster node 93110 a) are warranted relative to target node ID1 andmethod 9400 proceeds from step 9420 to step 9425.

At step 9425, method 9400 has the master node identifying at least oneneighboring node from the initial group of other nodes proximate to thetarget node's initial location. In one embodiment, the neighboring nodecomprises a single node from those within the initial group of othernodes. Such a single node may be located closer to the target nodecompared to at least a majority of the remaining nodes in the initialgroup of other nodes. For example, as shown in FIG. 87B, master node87110 a (modified to be implemented as master node 93110 a) may identifyID node ID2 (which may be paired with a package) as the neighboring nodethat will be temporarily pruned to cease broadcasting for a time (asexplained in more detail below).

In another embodiment, the neighboring node or nodes identified in step9425 may be a subgroup cluster of nodes from the initial group of othernodes proximate to the initial location of the target node. For example,as shown in FIG. 87C, master node 87110 a (modified to be implemented asmaster node 93110 a) may identify ID nodes ID2-ID6 as the neighboringnodes that will be temporarily pruned to cease broadcasting for a time(as explained in more detail below) in order to effect easiercommunication to and from target ID node ID1.

When “clustering” or identifying subgroup clusters of nodes from theinitial group of nodes proximate the target node's location, a furtherembodiment may have the master node identifying such subgroup clustersof nodes using a clustering parameter that distinguishes different nodeswithin the initial group. For example, a clustering parameter may beshipping information provided by the server to the master node andrelated to each node in the initial group of other nodes. Using suchshipping information as a clustering parameter, the master node mayidentify one subgroup cluster of nodes from the initial group asincluding those nodes having a first common destination address orlocation for delivery or transfer, while identifying another subgroupcluster of nodes from the initial group as including those nodes havinga second destination address or location for delivery or transfer.

In another example, the clustering parameter may involve context dataprovided by the server to the master node and relating to an anticipatedenvironment for each node in the initial group of other nodes duringpredicted movement of each node in the group of other nodes. Usingcontext data as the clustering parameter, the master node may identifyone subgroup cluster of nodes from the initial group as including thosenodes currently moving on a conveyor system (such as conveyor system87200), while identifying another subgroup cluster of nodes from theinitial group as including those nodes within a building (such as nodesstill located within storage location A 87205).

In still another example, the clustering parameter may involveassociation data identifying server-permitted logical relationshipsbetween different ones of the nodes in the initial group of other nodes.Using association data as the clustering parameter, the master node mayidentify one subgroup cluster of nodes from the initial group asincluding those nodes currently associated with one master node, whileidentifying another subgroup cluster of nodes from the initial group asincluding those nodes current associated within another master node inclose proximity to the target node.

At step 9430, method 9400 has the master node transmitting a change in abroadcast profile to the identified neighboring node(s) from the initialgroup given the operating node density exceeds the threshold. Thischange in the broadcast profile causes the neighboring node(s) totemporarily cease broadcasting during a first time interval. Thus, thismaster node initiated proactive operation changes the electroniccommunication landscape for the target node so to improve thecommunication operations of the target node in an unconventional manner.

When the neighboring node(s) are identified as a subgroup cluster ofnodes, a further embodiment of step 9430 may have the master nodetransmitting the change in the broadcast profile to each node in thesubgroup cluster of nodes given the operating node density exceeds thethreshold. This change in the broadcast profile causes each node in thesubgroup cluster of nodes to temporarily cease broadcasting during thefirst time interval.

In an embodiment that uses multiple subgroup clusters of nodes, anotherfurther embodiment of step 9430 may be implemented by identifying aplurality of subgroup clusters of nodes from the initial group of othernodes as the at least one neighboring node, and then having the masternode transmitting the change in the broadcast profile to each node inone or more of the subgroup clusters of nodes if the operating nodedensity exceeds the threshold. Such a change in the broadcast profilecauses each node in those different subgroup clusters of nodes totemporarily cease broadcasting during the first time interval.

At step 9435, method 9400 has the master node waiting until the end ofthe first time interval. During this time, the changes transmitted tothe appropriate neighboring nodes in step 9430 have those nodes ceasingtheir broadcasting activity so that the target node can more effectivelycommunicate in such a congested environment. But once the first timeinterval ends or expires, step 9435 proceeds to step 9440.

At step 9440, method 9400 proceeds to have the master node determine anupdated operating node density (UOND) of an updated group of other nodesin the plurality of wireless nodes proximate to an updated location ofthe target node. At this point in time, some of the nodes in thelogistics-related node network may have moved—including the target node.This dynamic aspect of such a logistics-related node network with mobilenodes causes the operational node landscape to change over time. As aresult, the updated location of the target node may be different whencompared by the master node to the initial location of the target node.Furthermore, given movement of the nodes, the updated group of othernodes may be different compared to the initial group of other nodes nearthe target node as previously located in step 9410.

If the master node determines in step 9445 that the updated operatingnode density (UOND) for the target node at its updated location isgreater than the threshold, then the target node is still deemed to bein a congested node landscape where master node-based communicationmanagement actions may be warranted to help locally reduce potentialcommunication interference from neighboring nodes. Thus, if the UOND isgreater than the threshold, step 9445 proceeds to step 9450. Otherwise,if the UOND is not greater than the threshold, the master node maypermit normal communications to occur with the regular broadcast profilesettings as they are with the neighboring nodes proximate the targetnode.

At step 9450, method 9400 proceeds with the master node identifying atleast one neighboring node from the updated group of the other nodeswithin a proximate range of the target node's updated location, and thenin step 9455 has the master node transmitting a further change in thebroadcast profile to at least one node from the updated group of othernodes proximate to the updated location of the target node given theupdated operating node density exceeds the threshold. This furtherchange in the broadcast profile causes the at least one node from theupdated group of other nodes to temporarily cease broadcasting during asecond time interval. Such a neighboring node or nodes from the updatedgroup may be just one node near the target node or a subgroup cluster ofmultiple nodes near the target node. Further still, the neighboringnodes caused to temporarily cease broadcasting during the second timeinterval may be a second subgroup cluster of nodes (distinct from or nothaving all of the same nodes as the first subgroup cluster of nodes thatwhere caused to temporarily cease broadcasting during the first timeinterval).

In still another further embodiment of method 9400, the master node mayidentify multiple updated subgroup clusters of nodes from the updatedgroup of other nodes proximate to the updated location of the targetnode once the first time interval expires as part of step 9450. As such,a further embodiment of step 9455 may have the master node transmittingthe further change in the broadcast profile to each node in a first ofthe updated subgroup clusters of nodes (to cause each node in the firstof the updated subgroup clusters of nodes to temporarily ceasebroadcasting during the second time interval). Alternatively, the masternode may transmit the further change in the broadcast profile to thefirst of the updated subgroup clusters during one part of the secondtime interval and then transmit the further change in broadcast profileto a second of the updated subgroup clusters during another part of thesecond time interval (e.g., another non-overlapping part of the secondtime interval or another partially overlapping part of the second timeinterval). Similar clustering parameters may be used by the master nodewhen identifying such updated neighboring nodes—whether single nodes, asubgroup cluster, or multiple subgroup clusters. Likewise, similarupdating of operating node density relative to a target node may beperformed by the master node after the second time interval expires andsimilar pruning/clustering communication management techniques may beenacted by the master node in still a third or subsequent time intervalas needed to help proactively create an improved node landscape relativeto the target node's location so that the target node may communicatemore effectively without undue interference.

Those skilled in the art will appreciate that method 9400 as disclosedand explained above in various embodiments may be implemented on amaster node apparatus, such as master node 87110 a illustrated in FIGS.87A-89B and modified to be implemented as master node 93110 a as shownin FIG. 93, running one or more parts of master control and managementcode 93425 (i.e., the high density node communication management code93000) and using exemplary node management rule data 93005. Such codeand data may be stored on a non-transitory computer-readable medium suchas memory storage 93415 on master node 87110 a (modified to beimplemented as master node 93110 a). Thus, when executing code 93425(that is implemented to include such high density node communicationmanagement code 93000), the master node's processing unit 93400 maybecome unconventionally operative to perform operations or steps fromthe exemplary methods disclosed above, including method 9400 andvariations of that method.

Those skilled in the art will appreciate that, when master nodes 87110 aand 87110 b as shown in FIGS. 87A-89B are implemented to embodyexemplary communication management master node 93110 a, a system-levelembodiment may include multiple communication management master nodes(each responsible enhanced communication management within differentparts of the wireless node network) and a server that provides theinitial instance of the particular node management rule for each ofthese master nodes as well as updates to those rules over time.

While method 9400 and its variations as described above focus onunconventional operations of an exemplary communication managementmaster node (such as master node 93110 a) as it enhances communicationmanagement for target nodes in a wireless node network, a further methodmay focus on more detailed operations of both such an exemplarycommunication management master node and the target node's neighboringnodes as they collectively provide enhanced communication management asa system to address an overly congested node operating environment.FIGS. 95A-95B are collectively a flow diagram illustrating anotherexemplary enhanced method of communication management of a plurality ofwireless nodes by a communication management master node and a targetnode's neighboring node(s) as they interact within a wireless nodenetwork in accordance with an embodiment of the invention.

In general, method 9500 includes specific steps performed by anexemplary communication management master node (similar to that shownand described above relative to method 9400 and its variations), butalso includes detailed steps performed by the identified neighboringnode(s) that are near the target node (e.g., steps 9535, 9540, 9550,9575, and 9580). In more detail and referring now to FIG. 95A, exemplarymethod 9500 begins at step 9505 with the master node identifying thetarget node from a subset of the wireless nodes in a logistics-relatedwireless node network (such as that shown in FIG. 87A). The subset ofwireless nodes identified are defined by a node management rule (such asthat stored in node management rule data 93005) received by the masternode from the server and stored within a memory of the master node. Inthis step, the target node is at an initial location, such as located ina storage location, relative to other nodes in the subset.

At step 9510, method 9500 proceeds with the master node identifying andlocating an initial group of other nodes that are within a predetermineddistance from the initial location of the target node. Thus, in theexample shown in FIG. 87B, master node 87110 a (modified to beimplemented as an exemplary communication management master node 93110a) may determine the location of ID nodes ID2-ID16 as being in aninitial group of other nodes within a particular distance from theinitial location of target node ID1. Each of ID nodes ID2-ID16 may be IDnodes that are attached to, associated with, or otherwise paired withdifferent packages.

At step 9515, method 9500 proceeds with the master node determining anoperating node density (OND) of the identified initial group of othernodes before proceeding to step 9520. If the determined operating nodedensity is not greater than a threshold value, method 9500 concludesgiven the identified target node is able to communicate effectively withan operating node density at a sufficiently low level to permit suchcommunication without interference from other surrounding nodes.However, if the determined operating node density is greater than athreshold value, step 9520 proceeds to step 9525.

At step 9525, method 9500 has the master node identifying at least oneneighboring node from the initial group of other nodes within theparticular distance from the target node's initial location. Aspreviously explained, such a neighboring node relative to a target nodemay be identified as one node, a group of several nodes (a subgroupcluster), or multiple groups of several nodes (multiple subgroupclusters) from those other nodes within the initial group near thetarget node. Stated another way, in one embodiment, a neighboring nodemay be identified by the master node in step 9525 as a single node inthe initial group (such as an ID node paired with a package) that islocated closer to the target node compared to at least a majority of theremaining nodes in the initial group. In another embodiment, theneighboring node identified by the master node in step 9525 may be oneor more subgroup clusters of multiple nodes from the initial group ofother nodes.

When identifying the neighboring nodes in step 9525, the master node mayrely upon a clustering parameter when identifying and categorizing someof the nodes in the initial group into the one or more subgroup clusterof nodes used as neighboring nodes for purposes of pruning to aidcommunication to and from the target node. For example and as explainedin more detail above, the clustering parameter used by the master nodemay be information received from a server and stored on the master node,such as shipping information related to each node in the initial group,context data related to an anticipated environment for each node in theinitial group of other nodes during predicted movement of each node inthe group of other nodes, or association data identifyingserver-permitted relationships between different nodes in the initialgroup.

With the one or more neighboring nodes identified in step 9525, method9500 proceeds to step 9530 where the master node transmits a broadcastprofile change message to the identified neighboring node(s) from theinitial group given the operating node density exceeds the threshold.Thus, when the neighboring node is a subgroup cluster of nodes, themaster node transmits the broadcast profile change message to each nodein the subgroup cluster of nodes as part of step 9530. As explained insteps 9535 and 9540 in more detail, the transmitted broadcast profilechange message causing each node in the subgroup cluster of nodes totemporarily cease broadcasting during the first time interval. In afurther embodiment when the master node identifies multiple subgroupclusters from nodes as potential neighboring nodes, the master node maytransmit the broadcast profile change message to each node in a first ofthe subgroup clusters of nodes, given the operating node density exceedsthe threshold, to cause each node in the first of the subgroup clustersof nodes to temporarily cease broadcasting during the first timeinterval. In another further embodiment, the master node may transmitthe broadcast profile change message to each node in a second of thesubgroup clusters of nodes after the first time interval expires and ifthe operating node density still exceeds the threshold. The broadcastprofile change message transmitted to each node in the second subgroupclusters of nodes causes a temporary cease of broadcasting for each nodein the second subgroup clusters of nodes during a second time interval.

At step 9535, method 9500 has the identified neighboring node(s)receiving the broadcast profile change message from the master node. Ifthe identified neighboring node is a master node, that master node maydirectly receive the broadcast profile change message from the masternode operating as the communication management master node (e.g., masternode 93110 a). However, when the identified neighboring node is an IDnode (such as a package ID node paired with a package or item beingshipped), that ID node may indirectly receive the broadcast profilechange message from the master node operating as the communicationmanagement master node.

At step 9540, method 9500 has the identified neighboring node(s)changing a broadcast profile resident and operating on that wirelessnode to a temporary silent mode. Such a temporary silent mode causesthat neighboring node to temporarily cease broadcasting during a firsttime interval. When the first time interval expires, method 9500proceeds from step 9545 through transition A to step 9550 in FIG. 95B.Referring now to FIG. 95B at step 9550, method 9500 proceeds with theidentified neighboring node(s) resetting their respective broadcastprofile to a previous broadcast mode in order to no longer preventnode(s) from broadcasting.

At step 9555, method 9500 proceeds with the master node determining anupdated operating node density (UOND) of an updated group of other nodesin the plurality of wireless nodes that are within the predetermineddistance from an updated location of the target node. Such an updatedlocation of the target node may be different compared to the targetnode's initial location if the target node has moved during the firsttime interval. Likewise, those skilled in the art will appreciate thatthe updated group of other nodes is different compared to the initialgroup of other nodes due to node movement. Thus, the updated operatingnode density related to the target node reflects a potentially changedoperating node landscape for the target node.

At step 9560, method 9500 has the master node determining if the updatedoperating node density is greater than the threshold value. If thedetermined updated operating node density is not greater than thethreshold value, step 9560 moves to the end of method 9500 as the targetnode now no longer needs master node-based enhanced communicationmanagement assistance in order to sufficiently communicate with othernodes. However, if the determined updated operating node density isgreater than the threshold value, step 9560 proceeds to step 9565.

At step 9565, method 9500 has the master node identifying at least asecond neighboring node or neighboring nodes to the target node from theupdated group of other nodes and then transmitting a further broadcastprofile change message to the identified second neighboring node(s) instep 9570. At step 9575, method 9500 has the identified secondneighboring node(s) receiving the broadcast profile change message fromthe master node. Then, at step 9580, method 9500 has the identifiedsecond neighboring node(s) changing a broadcast profile resident andoperating on the identified neighboring node(s) to the temporary silentmode that causes such nodes to temporarily cease broadcasting during asecond time interval.

In a further embodiment of method 9500, step 9565 may have the masternode (e.g., master node 87110 a modified to be implemented as anexemplary communication management master node 93110 a) identifyingmultiple updated subgroup clusters of nodes from the updated group ofother nodes in the plurality of wireless nodes that are within thepredetermined distance from an updated location of the target node. Withthese identified multiple updated subgroup clusters of nodes aspotential neighboring nodes that may be temporarily silenced, the masternode may transmit the further broadcast profile change message to eachnode in a first of the updated subgroup clusters of nodes given theupdated operating node density exceeds the threshold after the firsttime interval expires. This further broadcast profile change messagecauses each node in this first updated subgroup clusters of nodes totemporarily cease broadcasting during the second time interval.

Thereafter, the master node may also transmit the further broadcastprofile change message to each node in a second of the updated subgroupclusters of nodes after the second time interval expires and if theupdated operating node density still exceeds the threshold. At thispoint, the further broadcast profile change message transmitted by themaster node to each node in the second of the updated subgroup clustersof nodes causes a temporary cease of broadcasting for each node in thesecond of the updated subgroup clusters of nodes during a third timeinterval. As such, the communication management master node and thenodes operating as neighboring nodes relative to the target nodefunction as a type of system that enhances how the target node cancommunicate with other elements of a wireless node network.

As explained relative to exemplary method 9500 and the relatedvariations described above, a system-level embodiment may include acommunication management master node (such as master node 87110 amodified to be implemented as exemplary communication management masternode 93110 a) and one or more neighboring nodes relative to a targetnode. Such a master node and the neighboring node(s) for elements ofsuch an exemplary system for enhanced communication management thatimproves communications to and from the target node. Those skilled inthe art will appreciate that a further system-level embodiment maycomprise a server interacting with multiple master nodes that aredeployed as communication management master nodes (such as both ofmaster nodes 87110 a and 87110 b when both are implemented as exemplarycommunication master nodes similar to node 93110 a). Generally, in sucha further system-level embodiment, the server provides dedicated nodecommunication management rules to each of the master nodes and themaster nodes may conduct pruning operations that overlap in time thatseparately and independently enhance communication management of twodifferent target nodes during time intervals that may at least overlap(or over the same time interval). As such, the system may help twodifferent target nodes to communicate with each other or with othernodes.

FIGS. 96A-96B are collectively a flow diagram illustrating anotherexemplary enhanced method of communication management of a plurality ofwireless nodes by a server and multiple communication management masternodes as they interact within a wireless node network in accordance withan embodiment of the invention. Referring now to FIG. 96A, exemplarymethod 9600 illustrates an embodiment of a method of communicationmanagement of a plurality of wireless nodes disposed in a hierarchicalwireless node network having at least the plurality of wireless nodesdisposed at a low level in the network, a plurality of master nodesdisposed at a middle level in the network and physically located indifferent locations, and a server disposed at a top level in thenetwork.

Method 9600 begins at step 9605 with the server transmitting a differentdedicated node communication management rule to each of multiple masternodes (implemented as different communication management master nodes(CMMNs) similar to master node 93110 a). Each of the dedicated nodecommunication management rules (e.g., a master node specific rule storedas node management rule data 93005) assigns a different portion of thewireless nodes in the network to a respective one of the CMMNs. Forexample, as shown in FIG. 89A, a system embodiment may include server87100 that interacts directly with each of master nodes 87110 a and87110 b (which in this example may be implemented as an embodiment ofexemplary communication management master node 93110 a). As such and inthis example, server 87100 may transmitting a different dedicated nodecommunication management rule to each of CMMN 87110 a and 87110 b. Thededicated node communication management rule sent to CMMN 87110 aassigns ID nodes ID1-ID6, ID17, and ID18 to CMMN 87110 a for purposes ofcommunication management. Likewise, the dedicated node communicationmanagement rule sent to CMMN 87110 b assigns ID nodes IDT-16, andID19-ID21 to CMMN 87110 b for purposes of communication management.

At step 9610, method 9600 proceeds to have each of the master nodesreceive a respective one of the dedicated node communication managementrules from the server. With their respectively different dedicated nodecommunication management rules stored in onboard memory, each of themaster nodes may access their node communication management rules as atype of white list of appropriate wireless nodes within the network thatare the responsibility of that master node for purposes of enhancedcommunication management in congested node environments.

At step 9615, method 9600 proceeds with a first of the master nodes(1^(st) CMMN) identifying a first target node from within a firstportion of the wireless nodes (i.e., the portion of wireless nodesassigned to the 1^(st) CMMN). At this point, the first target node isdisposed at a first physical location. For example, in the example shownin FIG. 89A, master node 87110 a (as the 1^(st) CMMN) may identify IDnode ID1 as the first target node from those nodes assigned to masternode 87110 a pursuant to a dedicated node communication management rulereceived by master node 87100 a from server 87100.

At step 9620, method 9600 continues with the 1^(st) CMMN locating aninitial group of other nodes in the first portion of wireless nodes thatare within a threshold range relative to the first location of the firsttarget node. As such, in the example of FIG. 89A, master node 87110 aoperating as the 1^(st) CMMN may locate an initial group of other nodeswithin a threshold range of the location of ID node ID1 to include IDnodes ID2-ID6.

At step 9625, method 9600 proceeds to have the 1^(st) CMMN determine anoperating node density (OND1) of the initial group of other nodes in thefirst portion of wireless nodes, and then, at step 9630, determineswhether that operating node density if greater than a threshold value asa gauge of the operating node congestion near the first target node. Ifthe operating node density OND1 is not greater than the threshold value,then step 9630 proceeds directly through transition A to step 9645 (asshown in FIG. 96B). Otherwise, if the operating node density OND1 isfound to be greater than the congestion threshold value in step 9630,method 9600 proceeds to step 9635.

At step 9635, method 9600 proceeds to have the 1^(st) CMMN identify atleast one neighboring node near the first target node from the initialgroup of other nodes in the first portion of wireless nodes. Such aneighboring node relative to the first target node may be identified asone node, a group of several nodes (a subgroup cluster), or multiplegroups of several nodes (multiple subgroup clusters) from those othernodes within the initial group near the first target node (which maydetermine such subgroup clusters of node based upon different types ofclustering parameters).

At step 9640, method 9600 continues by having the 1^(st) CMMN transmit achange in a broadcast profile to the identified neighboring node(s) tocause the identified neighboring node(s) related to the first portion ofthe wireless nodes to temporarily cease broadcasting during a first timeinterval. Thereafter, method 9600 proceeds through transition A to step9645 in FIG. 96B.

Referring now to step 9645 in FIG. 96B, method 9600 proceeds with asecond of the master nodes (2^(nd) CMMN) identifying a second targetnode from within a second portion of the wireless nodes (i.e., theportion of wireless nodes assigned to the 2^(nd) CMMN). At this point,the second target node is disposed at a second physical location(different from the first physical location where the first target nodeis located). For example, in the example shown in FIG. 89A, master node87110 b (as the 2^(nd) CMMN) may identify ID node ID13 as the secondtarget node from those nodes assigned to master node 87110 b pursuant toa dedicated node communication management rule received by master node87100 b from server 87100.

At step 9650, method 9600 continues with the 2^(nd) CMMN locating aninitial group of other nodes in the second portion of wireless nodesthat are within a threshold range relative to the second location of thesecond target node. As such, in the example of FIG. 89A, master node87110 b operating as the 2^(nd) CMMN may locate an initial group ofother nodes within a threshold range of the location of ID node ID13 toinclude ID nodes ID7-ID12 and ID14-ID16.

At step 9655, method 9600 proceeds to have the 2^(nd) CMMN determine anoperating node density (OND2) of the initial group of other nodes in thesecond portion of wireless nodes, and then, at step 9660, determineswhether that operating node density if greater than a threshold value asa gauge of the operating node congestion near the second target node. Ifthe operating node density OND2 is not greater than the threshold value,then step 9660 proceeds and concludes method 9600. Otherwise, if theoperating node density OND2 is found to be greater than the congestionthreshold value in step 9660, method 9600 proceeds to step 9665.

At step 9665, method 9600 proceeds to have the 2^(nd) CMMN identify atleast one neighboring node near the second target node from the initialgroup of other nodes in the second portion of wireless nodes. Such aneighboring node relative to the second target node may be identified asone node, a group of several nodes (a subgroup cluster), or multiplegroups of several nodes (multiple subgroup clusters) from those othernodes within the initial group near the second target node (which maydetermine such subgroup clusters of node based upon different types ofclustering parameters).

At step 9670, method 9600 concludes by having the 2^(nd) CMMN transmit achange in a broadcast profile to the identified neighboring node(s) tocause the identified neighboring node(s) related to the second portionof the wireless nodes to temporarily cease broadcasting during a secondtime interval, which may be non-overlapping or have an overlapping timeperiod with respect to the first time interval.

In still another embodiment, a type of centralized communicationmanagement master node may be deployed with programmatically implementedfunctionality used to enhance centralized high density nodecommunication management via other master nodes. Generally, in such anenvironment, this type of centralized communication management masternode (also referred to as a “primary master node” for purposes ofenhanced communication management via pruning techniques) may bedeployed at a central position relative to a portion of the wirelessnode network. From this central position, the primary master nodegenerally functions as a network element that communicates with a serverwhile also communicating with other master nodes within a communicationrange of the primary master node. At this position relative to the othermaster nodes, the primary master node may be deployed as a primarycontroller of the other master nodes relative to enhanced communicationmanagement functions performed by each of the other master nodes.

In more detail, such an exemplary primary master node may be positioned,for example, at a general “RF centroid” location relative to the othermaster nodes so that the primary master node has similar (but notnecessarily identical) communication with each of the certain othermaster nodes being managed by that centralized pruning master node. Asexplained in more detail below, an exemplary primary master node mayalso be implemented with one or more improved communication interfacesthat use different radio and/or antenna technology that gives theprimary master node a different range/sensitivity for communicating withthe other master nodes over longer distances when compared toconventionally equipped master nodes that may be listening to theprimary master node. Thus, with such an exemplary primary master noderesponsible to managing other master nodes for purposes of enhancedcommunication management, an embodiment may include a mix of morepassive and active master nodes that interact as part of enhancingcommunication management and facilitating improved communications to andfrom a target node within the network in overly congested nodeenvironments.

FIGS. 97-99 illustrate various embodiments that include and leverage useof such an exemplary primary master node apparatus for purposes ofenhanced communication management within an overly congested nodeenvironment. More specifically, FIG. 97 is a diagram illustratingdetails of an exemplary primary master node 97110 a that controls othermaster nodes as part of providing enhanced communication management fora congested node environment in accordance with an embodiment of theinvention. Referring now to FIG. 97, exemplary centralized communicationmanagement master node 97110 a (commonly referred to as a “primarymaster node” for purposes of enhanced communication management) isillustrated in accordance with an embodiment of the invention that usescentralized high density node communication management code 97000 aspart of master control and management code 97425 to implement theenhanced communication management functionality on priority master node97110 a in an unconventional manner. Those skilled in the art willappreciate that exemplary primary master node 97110 a is shown in FIG.97 similar to master node 425 (previously described relative to FIG. 4);master nodes 87110 a and 87110 b (previously described as deployed inthe embodiments shown in FIGS. 87A-89B); and master node 93110 a(previously described as deployed in the embodiments shown in FIGS.94-96 b). More specifically, those skilled in the art will appreciatethat an embodiment of exemplary primary master node 97110 a includesmany of the same hardware, code, and data components as shown forexemplary master node 425 (as well as master nodes 87110 a, 87110 b, and93110 a). As such, similar functionality exists for what is numbered thesame or similarly and described above regarding exemplary master node425. Thus, while master node 425 shown in FIG. 4 is described as havingprocessing unit 400, memory storage 415, volatile memory 420,clock/timer 460, sensors 465, battery/power interface 470, GPS 475,short range communication interface 480, and medium/long rangecommunication interface 485, those skilled in the art will appreciatethat exemplary master node 97110 a may use similar hardware componentsas shown in FIG. 4. This includes at least processing unit 97400, memorystorage 97415, volatile memory 97420, clock/timer 97460, sensors 97465,battery/power interface 97470, GPS 97475, short range communicationinterface 97480, and medium/long range communication interface 97485.

Additionally, exemplary primary master node 97110 a deploys centralizedhigh density node communication management code 97000, which is storedin memory storage 97415 as part of master control and management code97425. Centralized high density node communication management code 97000may be loaded into volatile memory 97420 for execution by processingunit 97400. The master control and management code 425, as previouslydescribed, generally controls the behavior of a master node relating tocommunications (with a node advertise and query logic manager),information management (with an information control and exchangemanager), power management (with a node power manager that interactswith the various communication interfaces, for example, to manage powerconsumption and broadcast power aspects at a low level), associationmanagement (with an association manager), and location determinationfunctionality (with a location aware/capture module). As such, mastercontrol and management code 97425 essentially operates similar to thatas described above for master node control and management code 425 butfurther includes centralized high density node communication managementcode 97000 for functions used to coordinate and interact with othermaster nodes as part of providing enhanced communication management ofwireless nodes operating in a congested logistics node networkenvironment as described more detail below with respect the systemsshown in FIGS. 98A-98C and to the methods described relative to FIG. 99.Thus, an embodiment of centralized high density node communicationmanagement code 97000 may be implemented as an integrated part of mastercontrol and management code 97425, such as one or more programmaticfunctions or additional program modules that may be called within code97425. However, in other embodiments, the centralized high density nodecommunication management code 97000 used to implement the method asdescribed with respect to FIGS. 98A-98C and 99 may be implementedseparately from code 97425 in a way that allows code 97000 to call someof the programmatic functions or program modules described as part ofcode 425 (or 97425) to implement the steps as laid out in the methodillustrated in the flowchart of FIG. 94 and variations of that method asdescribed herein.

In general, exemplary centralized high density node communicationmanagement code 97000 programmatically adapts and transforms theoperation of exemplary primary master node 97110 a such that primarymaster node 97110 a unconventionally functions to receive acommunication from a server, which assigns the primary master node theparticular role of managing specific other master nodes and ID nodescollectively within a communication range of the primary master node. Inresponse, the primary master node then generally identify a target nodefrom those other master nodes and ID nodes; determine an operating nodedensity relative to that target node based upon locations known ordetermined by the primary master node of the target node and otherneighboring nodes; and cause one or more of the neighboring nodes totemporarily cease broadcasting for a particular time interval viatransmitted changes to those nodes' broadcast profiles. The primarymaster node may also determine an updated operating node density of anupdated group of master nodes and ID nodes within range of the targetnode, and transmit a further change in the broadcast profile to one ormore nodes from the updated group to cause those nodes to temporarilycease broadcasting during a subsequent time interval. And while theserver may assign the primary master node to be an active manager forenhanced communications related to the target node, the server may alsoassign the other master nodes to a passive role in such enhancedcommunication management relative to the target node in that the othermaster nodes must listen to the primary master node for direction andcontrol related to enhanced communication management relative to thetarget node via pruning and clustering techniques.

Additionally, an embodiment of primary master node 97110 a may implementits exemplary medium/long range communication interface 97485 with awireless transceiver that has enhanced performance compared to the othermaster nodes that operate in a passive role in such enhancedcommunication management relative to the target node. For example, themedium/long range communication interface 97485 in an embodiment ofprimary master node 97110 a may be implemented with a wirelesstransceiver having a larger broadcast power with which to transmitmessages (e.g., broadcast profile change messages and passive nodecommunication management rules) to other nodes compared to the broadcastpower for similar interfaces used in the other master nodes that operatein a passive role. Further enhancements to such a medium/long rangecommunication interface 97485 may include using multiple radios (e.g.,using dedicated radios for different passive master nodes) and/or usingantennas that may deploy multiple antenna elements capable ofbeam-forming to enhance, for example, a transmission pattern and rangefor the interface 97485 relative to different other passive masternodes.

FIGS. 98A-98C are diagrams illustrating an exemplary system 9800 oflogistics node elements that include an exemplary primary master node97110 a deployed to control other master and ID nodes as part ofproviding enhanced communication management for an overly congested nodeenvironment in accordance with an embodiment of the invention. Referringnow to FIG. 98A, those skilled in the art will appreciate that thesystem 9800 of network elements illustrated may be deployed in manner toprovide enhanced communication management for the congested nodeenvironment while substantially distributing the enhanced communicationmanagement responsibility down from a server-level of the network. Inparticular, exemplary system 9800 is shown as comprising a server 87100,a primary master node 97110 a, two other master nodes 87110 a, 87110 bwithin the communication range of primary master node 97110 a, and IDnodes ID1-ID21 (some or all of which being paired with a shipmentpackage that may be located at storage location A 87205, on conveyorsystem 87200, or in delivery vehicle storage area 87210).

As shown in the embodiment illustrated in FIGS. 98A-98C, the primarymaster node 97110 a in system 9800 may be disposed at an RF centroidrelative to the other master nodes 87110 a, 87110 b. In this position,the primary master node 97110 a may be deployed in a position thatprovides similar communications with each of the other masternodes—e.g., via relative distances to each of the other master nodesand/or relative transmission distances (which may take into account RFinterference and attenuation from surrounding structure) to each of theother master nodes). Primary master node 97110 a may also have with acommunication range that is greater than each of master nodes 87110 a,87110 b via an enhanced communication interface as discussed above.Thus, primary master node 97110 a may communicate with at least each ofmaster nodes 87110 a, 87110 b and, in some embodiments, also with eachof ID nodes ID1-ID21.

As part of system 9800, primary master node 97110 a is generally used tocontrol the other master nodes 87110 a, 87110 b as part of providingenhanced communication management. For example, in operation ofexemplary system 9800, server 87100 may transmit an active nodecommunication rule to the primary master node 97110 a. Upon receipt ofthis active node communication rule, the primary master node becomesassigned to operate as a primary master node managing specific othermaster nodes and ID nodes collectively within a communication range ofthe primary master node 97110 a. For example, as shown in the embodimentillustrated in FIG. 98A, primary master node 97110 a may receive such anactive node communication rule from server 87100, which assigns primarymaster node 97110 a with enhanced communication managementresponsibility for each of master nodes 87110 a and 87110 b as well asID nodes ID1-ID21.

Thereafter, primary master node 97110 a (in this active role) maytransmit passive node communication management rules to each of masternodes 87110 a and 87110 b. In another embodiment, the server 87100 mayalternatively transmit such passive node communication management rulesto each of master nodes 87110 a and 87110 b. Upon receipt of theirrespective passive node communication management rules, each of masternodes 87110 a and 87110 b becomes a passive listener for purposes ofenhanced communication management and allow primary master node 97110 ato control the process of pruning and, in some embodiments clustering,related to improving communications with a target node (such as one ofmaster nodes 87110 a and 87110 b or ID nodes ID1-ID21). In other words,in such a passive listener role per their respectively received passivenode communication management rule, the primary master node 97110 a (orserver 87100) causes each of the master nodes 87110 a and 87110 b tooperate as a passive “child” node under control of the primary masternode for enhanced communication management purposes related to overlycongested node environments. Thus, even if server 87100 provides thepassive node communication management rule, such a rule has the effectof causing the recipient master node to look at the primary master node97110 a for control and direction for purposes of enhanced communicationmanagement relative to a particular target node in the network.

As shown in the example illustrated in FIG. 98B, the primary master node97110 a of exemplary system 9800 begins the active management effort bygenerally identifying a target node, determining if the operating nodedensity relative to that target node warrants further enhancedcommunication management intervention by primary master node 97110 a,and (if necessary) pruning relevant neighboring nodes (as a single node,subgroup cluster of nodes, or multiple subgroup clusters of nodes asdescribed above) so as to cause it/them to temporarily ceasebroadcasting for a time period.

For example, in FIG. 98B, primary master node 97110 a has identified IDnode ID1 as a target node. Those skilled in the art will recognize thatin the example shown in FIGS. 98A-98C, the target node may be any ofmaster nodes 87110 a, 87110 b (listening as child nodes to primarymaster node 97110 a for purposes of enhanced communication management)and ID nodes ID1-ID21. As shown in FIG. 98C, primary master node 97110 athen determines that the operating node density of an initial group ofother nodes near target ID node ID1 (e.g., the group with a thresholdrange of target ID node ID1 including ID nodes ID2-ID16) is greater thana threshold value, which then causes the primary master node 97110 a toresponsively transmit a change in a broadcast profile to each ofneighboring nodes ID2-ID6 so as to cause them to temporarily ceasebroadcasting for a time period. Thus, the primary master node 97110 amay cause one or more neighboring nodes (such as one node near thetarget node, a group of several nodes (a subgroup cluster) near thetarget node, or multiple groups of several nodes (multiple subgroupclusters) near the target node) to temporarily cease broadcasting andtemporarily improve the ability of the target node to communicate duringthat time period.

A similar process may take place with primary master node 97110 a uponexpiration of the time period and re-assessment of what nodes are nearthe updated location of the target node, and whether an updatedoperating node density indicates the primary master node 97110 a shouldtransmit a further change to at least one neighboring node from anupdated group of nodes near the updated location of the target node.

FIG. 99 is a flow diagram illustrating an exemplary enhanced method ofcommunication management involving a plurality of wireless nodes thatleverages use of a primary master node that controls other master nodesin accordance with an embodiment of the invention. In this embodiment,the enhanced method of communication management may be performed bycertain elements of a hierarchical wireless node network having at leasta plurality of wireless ID nodes disposed at a low level in the network,multiple master nodes disposed at a middle level in the network andphysically located in different locations, and a server disposed at atop level in the network. In more detail, and referring now to FIG. 99,method 9900 begins at step 9905 where the server transmits an activenode communication management rule assigning a first of the master nodesto operate as a primary master node (e.g., primary master node 97110 a)that manages the other master nodes (e.g., master nodes 87110 a, 87110b) as well as the ID nodes (e.g., ID nodes ID1-ID21, each which beingpaired with a package being shipped) collectively within a communicationrange of the first master node.

At step 9910, method 9900 continues with the first master node receivingthe active node communication management rule from the server. Forexample, in the embodiment shown in FIGS. 98A-98C, one of the masternodes shown as part of system 9800 (i.e., primary master node 97110 a)receives the active node communication management rule in a message fromserver 87100. In one example, the active node communication managementrule may operate to initiate execution of an embodiment of centralizedhigh density communication management code 97000 on master node 97110 aso that master node 97110 a becomes operative to function as thepreviously described primary master node that manages and controls othermaster nodes and/or ID nodes collectively within the communication rangeof master node 97110 a. However, in another example, an embodiment ofthe centralized high density communication management code 97000 mayalready be running and simply waiting for receipt of the active nodecommunication management rule from server 87100 in order to proceedfurther.

At step 9915, an embodiment method 9900 may have the other master nodesreceiving a passive node communication management rule from either theserver or the first master node operating as the primary master node.Such a passive node communication management rule generally causes eachof the others master nodes to operate as a passive child node under thecontrol of the first master node (that is now actively operating as theprimary master node).

At step 9920, method 9900 has the first master node identifying a targetnode from the other master nodes and ID nodes collectively within thecommunication range of the first master node. The identified target nodeis disposed at a first location within the communication range of thefirst master node. For example, the primary master node 97110 a shown inFIG. 98B may identify ID node ID1 as a target node within thecommunication range of primary master node 97110 a.

At step 9925, method 9900 continues with the first master node (e.g.,primary master node 97110 a) locating an initial group from the othermaster nodes and/or ID nodes that are within a threshold range relativeto the target node's first location. Then, at step 9930, method 9900 hasthe first master node determining an operating node density (OND) of thelocated initial group of other nodes.

At step 9935, if the determined operating node density is greater than athreshold value (which may represent a tolerable operating node densitythreshold for a node landscape surrounding the target node), method 9900continues to step 9940. Otherwise, step 9935 concludes to an end ofmethod 9900.

At step 9940, method 9900 has the first master node identifying at leastone neighboring node from the initial group of other nodes. Such aneighboring node or nodes may be identified as a single node near thetarget node, a group of several nodes (a subgroup cluster) near thetarget node, or multiple groups of several nodes (multiple subgroupclusters) near the target node. For example, as shown in FIG. 98C, IDnodes ID2-ID6 may be identified by primary master node 97110 a to berelevant neighboring nodes of target ID node ID1 for purposes ofenhanced communication to and from ID node ID1.

Finally, at step 9945, method 9900 concludes with the first master nodetransmitting a change in a broadcast profile to the identifiedneighboring node or nodes. This transmitted change in the broadcastprofile causes those neighboring node from the initial group totemporarily cease broadcasting during a first time interval.

In a further embodiment, the first time interval has expired and thefirst master node (operating as a primary master node) determines anupdated operating node density of an updated group of the others masternodes and ID nodes that are within the threshold range relative to anupdated location of the target node. As such, the first master node maythen transmit a further change in the broadcast profile to at least onenode from the updated group if the updated operating node density of theupdated group exceeds the threshold once the first time intervalexpires. Such a further change in the broadcast profile causes the atleast one node (e.g., one or more neighboring nodes relative to wherethe target node is now located) from the updated group of other nodes totemporarily cease broadcasting during a second time interval.

Those skilled in the art will appreciate that at least steps 9910-9945of method 9900 as disclosed and explained above in various embodimentsmay be implemented on a master node programmed to operate as anexemplary primary master node, such as primary master node 97110 aillustrated in FIGS. 97-98C, running one or more parts of master controland management code 97425 (i.e., the centralized high density nodecommunication management code 97000). Such code may be stored on anon-transitory computer-readable medium such as memory storage 97415 onprimary master node 97110 a. Thus, when executing code 97425 (that isimplemented to include such centralized high density node communicationmanagement code 97000), the master node's processing unit 97400 maybecome unconventionally operative to perform operations or steps fromthe exemplary methods disclosed above, including method 9900 andvariations of that method.

In summary and in light of the above description of the variousembodiments, it should be emphasized that a sequence of operations toperform any of the methods and variations of the methods described inthe embodiments herein are merely exemplary, and that a variety ofsequences of operations may be followed while still being true and inaccordance with the principles of the present invention.

At least some portions of exemplary embodiments outlined above may beused in association with portions of other exemplary embodiments tobetter communicate with, manage, and locate nodes in a wireless nodenetwork or use such nodes and network elements as part of a hierarchicalnode network deployed in a logistics environment as a technical solutionto various technical logistics problems. Moreover, those skilled in theart will understand that at least some of the exemplary embodimentsdisclosed herein may be used independently from one another and/or incombination with one another and may have applications to devices andmethods not disclosed herein.

Those skilled in the art will also appreciate that embodiments mayprovide one or more advantages, and not all embodiments necessarilyprovide all or more than one particular advantage as set forth herein.Additionally, it will be apparent to those skilled in the art thatvarious modifications and variations can be made to the structures andmethodologies described herein. Thus, it should be understood that theinvention is not limited to the subject matter discussed in thedescription. Rather, the present invention is intended to covermodifications and variations.

What is claimed is:
 1. An active shipment management system within awireless network enabled vehicle and that interacts with a managing nodeexternal to the vehicle, the system comprising: an ID node associatedwith a package being shipped, the ID node being operative to broadcast aplurality of advertising signals when disposed within the vehicle; acontainer node disposed within the vehicle and associated with a storageunit maintained within the vehicle, the container node being operativeto receive one or more of the broadcasted advertising signals from theID node as part of determining a location of the ID node; and a vehiclenode disposed with the vehicle, the vehicle node providing a wirelesscommunication path from within the vehicle to the managing node externalto the vehicle, the vehicle node being further operative to broadcast amanagement request within the vehicle, the management request beingrelated to the package being shipped; wherein the container node, afterthe vehicle node broadcasts the management request, is further operativeto receive the broadcasted management request, identify the ID nodeassociated with the package based upon shipping information included inthe management request, verify the package is on the vehicle based uponthe location of the ID node as determined by the container node, andtransmit a verification message to the vehicle node indicating whetherthe package is verified as being on the vehicle; and wherein the vehiclenode, in response to the verification message, is further operative totransmit a shipment update message to the managing node external to thevehicle, the shipment update message being based upon the verificationmessage received by the vehicle node and indicating updated shippinginformation related to the package.
 2. The system of claim 1, whereinthe container node comprises one of a plurality of container nodesdisposed within the vehicle.
 3. The system of claim 1, wherein thecontainer node is further operative to determine a location within thestorage unit to be the location of the ID node in order to verify thepackage is on the vehicle.
 4. The system of claim 1, wherein the updatedshipping information comprises at least one from the group consisting ofan unloading instruction for the package relative to the location of theID node, an environmental condition information related to the packageand the location of the ID node, a package status indicating the packageis on the wireless network enabled vehicle, and a package statusindicating the package is not on the wireless network enabled vehicle.5. The system of claim 1 further comprising an environment control unitoperatively coupled to the ID node and associated with the package,wherein the ID node is responsive to a control message generated by thecontainer node and provided to the ID node to cause the ID node toadjust a setting of the environmental control unit.
 6. The system ofclaim 5, wherein the ID node includes at least one sensor that capturessensor data characterizing a status of the package; and wherein thecontrol message generated by the container node is based upon the sensordata as provided by the located ID node to the container node.
 7. Thesystem of claim 5, wherein the control message generated by thecontainer node provides at least one control parameter to the located IDnode to cause the environmental control unit to provide a desiredthermal effect on the package.
 8. The system of claim 1, wherein thecontainer node is further operative to transmit an imbalance warning tothe vehicle node when the container node identifies an imbalancecondition based upon (a) shipping information related to the package and(b) a comparison of the determined location of the ID node and aweight-related placement scheme.
 9. The system of claim 8, wherein theweight-related placement scheme is related to at least one of thevehicle or the storage unit associated with the container node.
 10. Thesystem of claim 8, wherein the vehicle node is further operative togenerate a vehicle imbalance notification in response to receiving theimbalance warning from the container node.
 11. The system of claim 1,wherein the container node is further operative to generate alocation-based unload instruction for the package upon verifying thepackage is on the vehicle and based upon the determined location of theID node.
 12. The system of claim 11, wherein the location-based unloadinstruction is based upon the location of the ID node within the storageunit.
 13. The system of claim 11, wherein the location-based unloadinstruction is based upon the location of the ID node within thevehicle.
 14. The system of claim 1, wherein the container node isfurther operative to update a location-based unload scheme for thevehicle based upon the location of the ID node.